Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45ddcaf4654f67ace03c7397b5162040f21daeaaa07f4a868eedf224a7d626b6

Tx prefix hash: d2e4644303e3b16caa3d9a7a4115d194a337634522573a2d357282437e009434
Tx public key: f758f73d86f7c760c41ddf021913a2731276b407284cbf1b34a980453823b5be
Timestamp: 1738202930 Timestamp [UCT]: 2025-01-30 02:08:50 Age [y:d:h:m:s]: 00:137:12:19:58
Block: 1208045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98255 RingCT/type: yes/0
Extra: 01f758f73d86f7c760c41ddf021913a2731276b407284cbf1b34a980453823b5be021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae6c3d35157c04c3dfb4c75d7eea2b81b4edcfce457f7cbfd6bb4862f7e4ba4 0.600000000000 1694772 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": 1208055, "vin": [ { "gen": { "height": 1208045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae6c3d35157c04c3dfb4c75d7eea2b81b4edcfce457f7cbfd6bb4862f7e4ba4" } } ], "extra": [ 1, 247, 88, 247, 61, 134, 247, 199, 96, 196, 29, 223, 2, 25, 19, 162, 115, 18, 118, 180, 7, 40, 76, 191, 27, 52, 169, 128, 69, 56, 35, 181, 190, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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