Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7c5b50a8cff16bce9736541574ce4ea674a122eeddb4be4291ca6bcb5369c2b

Tx prefix hash: bad23f78b56af176a37e8f02059ad1bb3576bddcd0566359eca3f87c95241c66
Tx public key: a227e9972d770242c1baa0ae355d1bdecfb7117f53087cea5727c3817e94e847
Timestamp: 1685902765 Timestamp [UCT]: 2023-06-04 18:19:25 Age [y:d:h:m:s]: 02:217:15:25:51
Block: 775117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 675411 RingCT/type: yes/0
Extra: 01a227e9972d770242c1baa0ae355d1bdecfb7117f53087cea5727c3817e94e847021100000001faf35c9c000000000000000000

1 output(s) for total of 1.658501158000 dcy

stealth address amount amount idx
00: 8e20bae875c7f6aab642238677206dc4a9da8f8de49b4d9a37cc759ab4ac54d0 1.658501158000 1224618 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": 775127, "vin": [ { "gen": { "height": 775117 } } ], "vout": [ { "amount": 1658501158, "target": { "key": "8e20bae875c7f6aab642238677206dc4a9da8f8de49b4d9a37cc759ab4ac54d0" } } ], "extra": [ 1, 162, 39, 233, 151, 45, 119, 2, 66, 193, 186, 160, 174, 53, 93, 27, 222, 207, 183, 17, 127, 83, 8, 124, 234, 87, 39, 195, 129, 126, 148, 232, 71, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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