Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d13f832c6e01f104c1206237f5715cba6b7c1b5c22e8709a3713e998a17f2fe9

Tx prefix hash: 68e5652dc5f64b3ecf4185a60492b28a8c6efe2de5c07cb137262ffc3325777f
Tx public key: ca939b6f55e30c2f56d54e566066d37f246a06d50a501a3e5c536a26711fc03f
Timestamp: 1699807750 Timestamp [UCT]: 2023-11-12 16:49:10 Age [y:d:h:m:s]: 01:176:03:37:58
Block: 890159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387096 RingCT/type: yes/0
Extra: 01ca939b6f55e30c2f56d54e566066d37f246a06d50a501a3e5c536a26711fc03f02110000000433af99f4000000000000000000

1 output(s) for total of 0.689499107000 dcy

stealth address amount amount idx
00: 2800b8709f2d7e3c1e7547847c771e8ccfe043d676e159f996e41e003419040d 0.689499107000 1346180 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": 890169, "vin": [ { "gen": { "height": 890159 } } ], "vout": [ { "amount": 689499107, "target": { "key": "2800b8709f2d7e3c1e7547847c771e8ccfe043d676e159f996e41e003419040d" } } ], "extra": [ 1, 202, 147, 155, 111, 85, 227, 12, 47, 86, 213, 78, 86, 96, 102, 211, 127, 36, 106, 6, 213, 10, 80, 26, 62, 92, 83, 106, 38, 113, 31, 192, 63, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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