Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f927effc0911e11b71fbf507d4aee8035e11eba18f30c6f1144456debe3a3e18

Tx prefix hash: 74f1f152738f2e12261a749ec3d50b91bcad9a37d11bd9c0c9d0cbeb4179a695
Tx public key: a9dfbf9f4e063c5b366166aa0f1dd0217347f96f19c8bc5b073a307ac8127d92
Timestamp: 1737254844 Timestamp [UCT]: 2025-01-19 02:47:24 Age [y:d:h:m:s]: 00:057:00:01:17
Block: 1200420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40554 RingCT/type: yes/0
Extra: 01a9dfbf9f4e063c5b366166aa0f1dd0217347f96f19c8bc5b073a307ac8127d920211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d886640f929bbcb1086db44c6a4c255c4d38bd03d0800da8f479fe517094759b 0.600000000000 1687063 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": 1200430, "vin": [ { "gen": { "height": 1200420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d886640f929bbcb1086db44c6a4c255c4d38bd03d0800da8f479fe517094759b" } } ], "extra": [ 1, 169, 223, 191, 159, 78, 6, 60, 91, 54, 97, 102, 170, 15, 29, 208, 33, 115, 71, 249, 111, 25, 200, 188, 91, 7, 58, 48, 122, 200, 18, 125, 146, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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