Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b6cbc94a542b009fc60c2f8efd2ddea6e5915d729b11912f54e1777d359dbb1

Tx prefix hash: f3987a4e6bc94ecdd09f31d42880ba4ca42a5f29c2561747f5deb91a27750f6f
Tx public key: c996ea3af108319303253808c6a129f022d6e12a4ea801eb0b8cfe539b1336b3
Timestamp: 1726464694 Timestamp [UCT]: 2024-09-16 05:31:34 Age [y:d:h:m:s]: 00:196:13:26:09
Block: 1111146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140311 RingCT/type: yes/0
Extra: 01c996ea3af108319303253808c6a129f022d6e12a4ea801eb0b8cfe539b1336b3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ebabdae3b4d1183414776984c939f891d00a1318010aeb80ec6eeaec2a72907 0.600000000000 1590005 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": 1111156, "vin": [ { "gen": { "height": 1111146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ebabdae3b4d1183414776984c939f891d00a1318010aeb80ec6eeaec2a72907" } } ], "extra": [ 1, 201, 150, 234, 58, 241, 8, 49, 147, 3, 37, 56, 8, 198, 161, 41, 240, 34, 214, 225, 42, 78, 168, 1, 235, 11, 140, 254, 83, 155, 19, 54, 179, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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