Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b240cd5a5bc18a88bc635fa6c2b8c9f56598f73f35dc0f2098fc4d6fe3fad9f

Tx prefix hash: 06e223d248ddbc4aaf518b87865a7e286699219f35bcb7feba2c759e6e5d6cf8
Tx public key: ef0bc3918e336730311e788f83cca8210ecdd152b4cf7d0f450801611ceb7be3
Timestamp: 1680599410 Timestamp [UCT]: 2023-04-04 09:10:10 Age [y:d:h:m:s]: 01:291:07:38:58
Block: 731679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469158 RingCT/type: yes/0
Extra: 01ef0bc3918e336730311e788f83cca8210ecdd152b4cf7d0f450801611ceb7be3021100000001b3164c24000000000000000000

1 output(s) for total of 2.310170153000 dcy

stealth address amount amount idx
00: a168763b6d323c938d07443f02cb6ad3d758ea52e9bbd0840d86c0b210c362f5 2.310170153000 1177482 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": 731689, "vin": [ { "gen": { "height": 731679 } } ], "vout": [ { "amount": 2310170153, "target": { "key": "a168763b6d323c938d07443f02cb6ad3d758ea52e9bbd0840d86c0b210c362f5" } } ], "extra": [ 1, 239, 11, 195, 145, 142, 51, 103, 48, 49, 30, 120, 143, 131, 204, 168, 33, 14, 205, 209, 82, 180, 207, 125, 15, 69, 8, 1, 97, 28, 235, 123, 227, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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