Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 953fdee9a48f9cdd1d2a55b6bce5e5bdf55b894b61a81b1dec7f89553104a6a5

Tx prefix hash: 9feb064cf6f7a1c92d2340ae5a63f55a9511b487358d90cc0b20567eb9b9b148
Tx public key: 041ce913ba58564f68a5ab81c92a868926a8008da48345a5c9c3c81edf4aaf58
Timestamp: 1577099074 Timestamp [UCT]: 2019-12-23 11:04:34 Age [y:d:h:m:s]: 05:314:01:45:45
Block: 29933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1372007 RingCT/type: yes/0
Extra: 01041ce913ba58564f68a5ab81c92a868926a8008da48345a5c9c3c81edf4aaf58021100000003d81c26c0000000000000000000

1 output(s) for total of 488.492080284000 dcy

stealth address amount amount idx
00: f28755bb031a6bafcb6a13dc4e6b6911428d3b306e41d068a17aef9b08c86796 488.492080284000 49391 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": 29943, "vin": [ { "gen": { "height": 29933 } } ], "vout": [ { "amount": 488492080284, "target": { "key": "f28755bb031a6bafcb6a13dc4e6b6911428d3b306e41d068a17aef9b08c86796" } } ], "extra": [ 1, 4, 28, 233, 19, 186, 88, 86, 79, 104, 165, 171, 129, 201, 42, 134, 137, 38, 168, 0, 141, 164, 131, 69, 165, 201, 195, 200, 30, 223, 74, 175, 88, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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