Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcc380afedf9f22cff78750d2e122a3cf917c2ffd3c4814e9bef53244679e5ea

Tx prefix hash: 13594331c47d515e0f4d8607bd91a16baa00d2992b920a41da239124f7f538a2
Tx public key: 9185c86280219fcc51d3d3547b6b1643a5470b4dd36cc7a2b04ab8fb8bb56bae
Timestamp: 1721680330 Timestamp [UCT]: 2024-07-22 20:32:10 Age [y:d:h:m:s]: 00:296:07:24:39
Block: 1071479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211718 RingCT/type: yes/0
Extra: 019185c86280219fcc51d3d3547b6b1643a5470b4dd36cc7a2b04ab8fb8bb56bae021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc63c463d945ad8c635fd22375bbf4a92cfda639538415ab6ee1997f54e4521b 0.600000000000 1543724 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": 1071489, "vin": [ { "gen": { "height": 1071479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc63c463d945ad8c635fd22375bbf4a92cfda639538415ab6ee1997f54e4521b" } } ], "extra": [ 1, 145, 133, 200, 98, 128, 33, 159, 204, 81, 211, 211, 84, 123, 107, 22, 67, 165, 71, 11, 77, 211, 108, 199, 162, 176, 74, 184, 251, 139, 181, 107, 174, 2, 17, 0, 0, 0, 5, 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