Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5aa7f49474054fa2d1c08e36ae035140ee197945b561a30f89ca623a33e68a1d

Tx prefix hash: 608d8ac8ab2fa23837fd88377475d5ddb3d1a2af3ed524f8fa26da852f480e0d
Tx public key: 85a6250544e210ecba13a035ae0ffe3e8eb410fd2c20b7ed84bf09d02bb1a789
Timestamp: 1713556762 Timestamp [UCT]: 2024-04-19 19:59:22 Age [y:d:h:m:s]: 01:196:14:19:52
Block: 1004119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399173 RingCT/type: yes/0
Extra: 0185a6250544e210ecba13a035ae0ffe3e8eb410fd2c20b7ed84bf09d02bb1a78902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 285a4618f27b306ef3a8f3830c3ec7fd518a06eeb372893dde17388a2e6ce80c 0.600000000000 1464687 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": 1004129, "vin": [ { "gen": { "height": 1004119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "285a4618f27b306ef3a8f3830c3ec7fd518a06eeb372893dde17388a2e6ce80c" } } ], "extra": [ 1, 133, 166, 37, 5, 68, 226, 16, 236, 186, 19, 160, 53, 174, 15, 254, 62, 142, 180, 16, 253, 44, 32, 183, 237, 132, 191, 9, 208, 43, 177, 167, 137, 2, 17, 0, 0, 0, 5, 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