Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 770b0159ab08aa2adf6fcf01597d5d303e8945965b760e0c369955a419329eac

Tx prefix hash: 5344b75101dfc5e8849607d6a5ed1b027552df288ac451833e162084b87c3089
Tx public key: 0cc223281a8b9a06cc4ae05991c96fdf7acc1dffd3c43d7c734c221f576f1717
Timestamp: 1694462808 Timestamp [UCT]: 2023-09-11 20:06:48 Age [y:d:h:m:s]: 01:269:23:29:29
Block: 846024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454099 RingCT/type: yes/0
Extra: 010cc223281a8b9a06cc4ae05991c96fdf7acc1dffd3c43d7c734c221f576f171702110000000475e3f0e9000000000000000000

1 output(s) for total of 0.965542399000 dcy

stealth address amount amount idx
00: d12052d832d205f8f12414fb6f3a81f684a5a47652333f0ae8f79a0c495be1ce 0.965542399000 1299460 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": 846034, "vin": [ { "gen": { "height": 846024 } } ], "vout": [ { "amount": 965542399, "target": { "key": "d12052d832d205f8f12414fb6f3a81f684a5a47652333f0ae8f79a0c495be1ce" } } ], "extra": [ 1, 12, 194, 35, 40, 26, 139, 154, 6, 204, 74, 224, 89, 145, 201, 111, 223, 122, 204, 29, 255, 211, 196, 61, 124, 115, 76, 34, 31, 87, 111, 23, 23, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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