Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b1ca5ca9beaaf15259c6e480435dc5160d3f3540b3acf993d1cff1ad4ba3a8

Tx prefix hash: 7fc58b44f0e2f37093df33f8778e82a3853d2d2a8c668765568f03425d9c46d2
Tx public key: 9faf849e9a985691e887cd1dbf3ef762eb92a7ef3e34902fe72d61de9c3059cb
Timestamp: 1702319290 Timestamp [UCT]: 2023-12-11 18:28:10 Age [y:d:h:m:s]: 01:016:02:31:36
Block: 910975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272857 RingCT/type: yes/0
Extra: 019faf849e9a985691e887cd1dbf3ef762eb92a7ef3e34902fe72d61de9c3059cb021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bb0e1a14f63852a531210080f76fe3dfcc156ff5184ca33fa9410a97a27c372 0.600000000000 1368150 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": 910985, "vin": [ { "gen": { "height": 910975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bb0e1a14f63852a531210080f76fe3dfcc156ff5184ca33fa9410a97a27c372" } } ], "extra": [ 1, 159, 175, 132, 158, 154, 152, 86, 145, 232, 135, 205, 29, 191, 62, 247, 98, 235, 146, 167, 239, 62, 52, 144, 47, 231, 45, 97, 222, 156, 48, 89, 203, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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