Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25ba9bfedccf555baba4522ab12ffbdf03b1a6804e60c06e06652ba508c587f7

Tx prefix hash: 18d01810efd0dd2c975b2354f434b878ff2a1e177ea8ec7b0440f9b9ce65ff00
Tx public key: fe72e0e996925c37bc0d447ef009b13dd8fd02f3dd8b3507d4887265c3e88049
Timestamp: 1639356054 Timestamp [UCT]: 2021-12-13 00:40:54 Age [y:d:h:m:s]: 03:347:09:19:00
Block: 394255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1024774 RingCT/type: yes/0
Extra: 01fe72e0e996925c37bc0d447ef009b13dd8fd02f3dd8b3507d4887265c3e880490211000000040eb261b4000000000000000000

1 output(s) for total of 30.315859232000 dcy

stealth address amount amount idx
00: e60a1d81fb1c612c022b883e48e1abfa830569a4f644deb6b1c8062a11e585d2 30.315859232000 791786 of 0

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": 394265, "vin": [ { "gen": { "height": 394255 } } ], "vout": [ { "amount": 30315859232, "target": { "key": "e60a1d81fb1c612c022b883e48e1abfa830569a4f644deb6b1c8062a11e585d2" } } ], "extra": [ 1, 254, 114, 224, 233, 150, 146, 92, 55, 188, 13, 68, 126, 240, 9, 177, 61, 216, 253, 2, 243, 221, 139, 53, 7, 212, 136, 114, 101, 195, 232, 128, 73, 2, 17, 0, 0, 0, 4, 14, 178, 97, 180, 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