Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3b19305fc5958cb39bc8d61e1c8baffeef955dbdc8e01bbe36a6a57e496ae5c

Tx prefix hash: 929f9c9a6c8c9442e68fdf53e81c5c8398685c359c8f3c4df5c9ef7c63110473
Tx public key: 56bc1581c6324fde2fe80720a53aab85302b37dccf6bca4a6b63c9aa3e871b7a
Timestamp: 1701005658 Timestamp [UCT]: 2023-11-26 13:34:18 Age [y:d:h:m:s]: 01:089:19:57:48
Block: 900077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325330 RingCT/type: yes/0
Extra: 0156bc1581c6324fde2fe80720a53aab85302b37dccf6bca4a6b63c9aa3e871b7a02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.639250745000 dcy

stealth address amount amount idx
00: 17ca31fd4d4779ae0a20ff528d0ae79458617bfb3961eaacdd3906eeddcd6b12 0.639250745000 1356554 of 0

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": 900087, "vin": [ { "gen": { "height": 900077 } } ], "vout": [ { "amount": 639250745, "target": { "key": "17ca31fd4d4779ae0a20ff528d0ae79458617bfb3961eaacdd3906eeddcd6b12" } } ], "extra": [ 1, 86, 188, 21, 129, 198, 50, 79, 222, 47, 232, 7, 32, 165, 58, 171, 133, 48, 43, 55, 220, 207, 107, 202, 74, 107, 99, 201, 170, 62, 135, 27, 122, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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