Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd59b91d432b648699c444d68c5c131b80d224ba143447748bc039569731fa4c

Tx prefix hash: 101183e839fc5d117e4f018ffb809f19c0c636730b38729cf2fd9b43ee95563a
Tx public key: 83141bd7317d1c5a6bfcda2f8f40a88e8b3a3e267303fe9adcdb9872f501b493
Timestamp: 1719869816 Timestamp [UCT]: 2024-07-01 21:36:56 Age [y:d:h:m:s]: 00:212:07:43:54
Block: 1056471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151664 RingCT/type: yes/0
Extra: 0183141bd7317d1c5a6bfcda2f8f40a88e8b3a3e267303fe9adcdb9872f501b4930211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f04c443d91a8dadc46548bea2d33b577327516626fd7fee5deb59407c3d198e 0.600000000000 1526884 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": 1056481, "vin": [ { "gen": { "height": 1056471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f04c443d91a8dadc46548bea2d33b577327516626fd7fee5deb59407c3d198e" } } ], "extra": [ 1, 131, 20, 27, 215, 49, 125, 28, 90, 107, 252, 218, 47, 143, 64, 168, 142, 139, 58, 62, 38, 115, 3, 254, 154, 220, 219, 152, 114, 245, 1, 180, 147, 2, 17, 0, 0, 0, 2, 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