Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da5497cb4b063893f6abd35dd7246b38b611011f5f42dae8052e460b56e42514

Tx prefix hash: 3c01b603ffc9c35afcb791dc63c16fd9c2a6f102080bd5b0b8b620e4815fb943
Tx public key: 55cf115081a8a5a9a16988370853ce1092333a0bc1a553e8f7cf10c9ae4008d2
Timestamp: 1725742554 Timestamp [UCT]: 2024-09-07 20:55:54 Age [y:d:h:m:s]: 00:217:09:44:21
Block: 1105169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155213 RingCT/type: yes/0
Extra: 0155cf115081a8a5a9a16988370853ce1092333a0bc1a553e8f7cf10c9ae4008d2021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05cfe3dba596de97ec7f5a3746e6dc2fdf21c669a4e34ab4b591f33148aa7d4e 0.600000000000 1582508 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": 1105179, "vin": [ { "gen": { "height": 1105169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05cfe3dba596de97ec7f5a3746e6dc2fdf21c669a4e34ab4b591f33148aa7d4e" } } ], "extra": [ 1, 85, 207, 17, 80, 129, 168, 165, 169, 161, 105, 136, 55, 8, 83, 206, 16, 146, 51, 58, 11, 193, 165, 83, 232, 247, 207, 16, 201, 174, 64, 8, 210, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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