Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 469a2adb98440f124004d43442fe6f04e224f8180bcd8351a7a769ab0e715d55

Tx prefix hash: 80c044648180f85f0768e0f87d533ed0864f01a5d48558b66d2a2baf0ab3c76e
Tx public key: 2ccf31bbdad350666795fdc70e3b659b746e4f800512443bdb9b6c8e2f7c1db6
Timestamp: 1731317198 Timestamp [UCT]: 2024-11-11 09:26:38 Age [y:d:h:m:s]: 00:132:00:21:53
Block: 1151282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94184 RingCT/type: yes/0
Extra: 012ccf31bbdad350666795fdc70e3b659b746e4f800512443bdb9b6c8e2f7c1db6021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc6240b55b740c0b79da7cbce0c58940bdb98f14852c2788398a4a453e844b97 0.600000000000 1636783 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": 1151292, "vin": [ { "gen": { "height": 1151282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc6240b55b740c0b79da7cbce0c58940bdb98f14852c2788398a4a453e844b97" } } ], "extra": [ 1, 44, 207, 49, 187, 218, 211, 80, 102, 103, 149, 253, 199, 14, 59, 101, 155, 116, 110, 79, 128, 5, 18, 68, 59, 219, 155, 108, 142, 47, 124, 29, 182, 2, 17, 0, 0, 0, 6, 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