Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc1f45e800d24a43d8005720295a29a5acbee85541f5506ed62fc84e43defb18

Tx prefix hash: 132b96490889952d2041f41f545d3f82d47c4b791a514bc8d351ecdf25f964b3
Tx public key: 5ee966fc2b126eb481b37961f326f2d91903f48e6b07a7a43068614d4ec61340
Timestamp: 1713283246 Timestamp [UCT]: 2024-04-16 16:00:46 Age [y:d:h:m:s]: 00:354:22:21:30
Block: 1001846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253752 RingCT/type: yes/0
Extra: 015ee966fc2b126eb481b37961f326f2d91903f48e6b07a7a43068614d4ec6134002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6a631ec327ed027b8125d8b06de058aaa483fdc30a623f3c690f325e9a1d185 0.600000000000 1462358 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": 1001856, "vin": [ { "gen": { "height": 1001846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6a631ec327ed027b8125d8b06de058aaa483fdc30a623f3c690f325e9a1d185" } } ], "extra": [ 1, 94, 233, 102, 252, 43, 18, 110, 180, 129, 179, 121, 97, 243, 38, 242, 217, 25, 3, 244, 142, 107, 7, 167, 164, 48, 104, 97, 77, 78, 198, 19, 64, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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