Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2f7c2553559674811e34cfe496931af0210c83340e8926c67446759c0a9fcda

Tx prefix hash: 221f107b27a6cdd4f2aa69ba0e8a7f66717ab64593550d43712aaa99df4b29a2
Tx public key: 218ce319df51d2e772174509cfe1d5fd2117e843420d328d47185d0dcab71bd4
Timestamp: 1705744923 Timestamp [UCT]: 2024-01-20 10:02:03 Age [y:d:h:m:s]: 01:089:02:18:09
Block: 939341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324798 RingCT/type: yes/0
Extra: 01218ce319df51d2e772174509cfe1d5fd2117e843420d328d47185d0dcab71bd40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0b3e408048b7ce9cd017ef98a5fd104fe3f3442d096279b04c0922d29767fd1 0.600000000000 1397435 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": 939351, "vin": [ { "gen": { "height": 939341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0b3e408048b7ce9cd017ef98a5fd104fe3f3442d096279b04c0922d29767fd1" } } ], "extra": [ 1, 33, 140, 227, 25, 223, 81, 210, 231, 114, 23, 69, 9, 207, 225, 213, 253, 33, 23, 232, 67, 66, 13, 50, 141, 71, 24, 93, 13, 202, 183, 27, 212, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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