Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a40f88baf79b6e576a5b1f1af9b09048dc2d9ef59a21bf5b0acedabd48ce364

Tx prefix hash: b46ef4c22b209020ecf95a04e1f7f3958380d6ad3783e551e3a62ea70cd138f9
Tx public key: de52c5de173144090baf189fff4cdc4344e5a977dfca33017be17b3ea8f3fdf7
Timestamp: 1711294733 Timestamp [UCT]: 2024-03-24 15:38:53 Age [y:d:h:m:s]: 01:085:15:19:27
Block: 985404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322090 RingCT/type: yes/0
Extra: 01de52c5de173144090baf189fff4cdc4344e5a977dfca33017be17b3ea8f3fdf70211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3531e8227cbca3374dbe2f47d72e2abba415bdb919ca53f4b2386f3718df14fa 0.600000000000 1445613 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": 985414, "vin": [ { "gen": { "height": 985404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3531e8227cbca3374dbe2f47d72e2abba415bdb919ca53f4b2386f3718df14fa" } } ], "extra": [ 1, 222, 82, 197, 222, 23, 49, 68, 9, 11, 175, 24, 159, 255, 76, 220, 67, 68, 229, 169, 119, 223, 202, 51, 1, 123, 225, 123, 62, 168, 243, 253, 247, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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