Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b01c54e202096dd1ad7f06c4f2f1bc037fa5645854044284d73fae27afa638d4

Tx prefix hash: 6a2faebe19c10d9bbab882b332f893887d2d3c0dee28dd0ada0012f2338d8bc7
Tx public key: b3fb56e5a1c64f410987022d4726bebd35d0ea7e8767e3c26f7d43e318f5e62e
Timestamp: 1649775001 Timestamp [UCT]: 2022-04-12 14:50:01 Age [y:d:h:m:s]: 03:203:07:20:35
Block: 478680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 923534 RingCT/type: yes/0
Extra: 01b3fb56e5a1c64f410987022d4726bebd35d0ea7e8767e3c26f7d43e318f5e62e0211000000015eb576c5000000000000000000

1 output(s) for total of 15.919692956000 dcy

stealth address amount amount idx
00: e80a1495c6450b9f4aaa4e9a78aedd0d7bf1edcc724d0b4a685d191374403608 15.919692956000 899471 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": 478690, "vin": [ { "gen": { "height": 478680 } } ], "vout": [ { "amount": 15919692956, "target": { "key": "e80a1495c6450b9f4aaa4e9a78aedd0d7bf1edcc724d0b4a685d191374403608" } } ], "extra": [ 1, 179, 251, 86, 229, 161, 198, 79, 65, 9, 135, 2, 45, 71, 38, 190, 189, 53, 208, 234, 126, 135, 103, 227, 194, 111, 125, 67, 227, 24, 245, 230, 46, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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