Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a1418b72f116e228656f0225a077ec0d31dc6b7e6ba56d616acf0b77efc9ad5

Tx prefix hash: c605488ded84c54e94ad22d24b0181906af3ca5b4f7fd13ae2ba7ee3cad712d5
Tx public key: cc2468c8caccb266b1052ee4f3162d11fcef631409ce226f1131bc3668cf835f
Timestamp: 1701264350 Timestamp [UCT]: 2023-11-29 13:25:50 Age [y:d:h:m:s]: 01:166:13:20:50
Block: 902227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380219 RingCT/type: yes/0
Extra: 01cc2468c8caccb266b1052ee4f3162d11fcef631409ce226f1131bc3668cf835f021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.628850480000 dcy

stealth address amount amount idx
00: 009460981662030a45c5c22e4355efea15f3c46c8d3dd8dacbda64d5f17464e9 0.628850480000 1358846 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": 902237, "vin": [ { "gen": { "height": 902227 } } ], "vout": [ { "amount": 628850480, "target": { "key": "009460981662030a45c5c22e4355efea15f3c46c8d3dd8dacbda64d5f17464e9" } } ], "extra": [ 1, 204, 36, 104, 200, 202, 204, 178, 102, 177, 5, 46, 228, 243, 22, 45, 17, 252, 239, 99, 20, 9, 206, 34, 111, 17, 49, 188, 54, 104, 207, 131, 95, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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