Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeecec482cf24f5aacede931d7d986b0ad96ec009b16ede327159c6c44ea0480

Tx prefix hash: 4a9f2fb8e31a0916e9fc699a4abe997b38070e867088b1309ced114946506bb3
Tx public key: 6cde852822418c26c1d5b4e3df6d62254eb585faf8753cc5d9826ffa74fee302
Timestamp: 1680004020 Timestamp [UCT]: 2023-03-28 11:47:00 Age [y:d:h:m:s]: 01:290:17:50:01
Block: 726867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468665 RingCT/type: yes/0
Extra: 016cde852822418c26c1d5b4e3df6d62254eb585faf8753cc5d9826ffa74fee302021100000001b3164c24000000000000000000

1 output(s) for total of 2.396559022000 dcy

stealth address amount amount idx
00: fbe3cee2a8e2f0394bc49ad997c78afe5510c262a961d089c6e16bb0f05c1913 2.396559022000 1172134 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": 726877, "vin": [ { "gen": { "height": 726867 } } ], "vout": [ { "amount": 2396559022, "target": { "key": "fbe3cee2a8e2f0394bc49ad997c78afe5510c262a961d089c6e16bb0f05c1913" } } ], "extra": [ 1, 108, 222, 133, 40, 34, 65, 140, 38, 193, 213, 180, 227, 223, 109, 98, 37, 78, 181, 133, 250, 248, 117, 60, 197, 217, 130, 111, 250, 116, 254, 227, 2, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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