Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b7d84b6e9314c11d36078d7c9e037d054ea8f3a663293b32dbae2a763a4cd91e

Tx prefix hash: 9a8cf662ffc025c5869fb807bf18240ed9c687e3134736abbc3bf5f1639e9765
Tx public key: efa63631069f9fb312346ed8b210e6192bfac537e32922f32b2a92a7acb0a36d
Timestamp: 1737245812 Timestamp [UCT]: 2025-01-19 00:16:52 Age [y:d:h:m:s]: 00:155:06:53:17
Block: 1200350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110628 RingCT/type: yes/0
Extra: 01efa63631069f9fb312346ed8b210e6192bfac537e32922f32b2a92a7acb0a36d021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 286cd141e0806621a6dca1dcfdcca9c5b925625b3986ec935835ecf230b55a16 0.600000000000 1686993 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1200360, "vin": [ { "gen": { "height": 1200350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "286cd141e0806621a6dca1dcfdcca9c5b925625b3986ec935835ecf230b55a16" } } ], "extra": [ 1, 239, 166, 54, 49, 6, 159, 159, 179, 18, 52, 110, 216, 178, 16, 230, 25, 43, 250, 197, 55, 227, 41, 34, 243, 43, 42, 146, 167, 172, 176, 163, 109, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8