Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d5e465845525056c240fbe301a20054f68ca5d49d38d4d8c6f6c60c3cd0c27

Tx prefix hash: 20c2a54a2e31f95402870ebef615b13e0e39a961e61d5e87e6c2ddb0cc642c5c
Tx public key: f934c289b0571071d75c9dcf27de6082009cb54b546ed09d2324edc8104985b4
Timestamp: 1583538515 Timestamp [UCT]: 2020-03-06 23:48:35 Age [y:d:h:m:s]: 04:351:15:41:52
Block: 77883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145559 RingCT/type: yes/0
Extra: 01f934c289b0571071d75c9dcf27de6082009cb54b546ed09d2324edc8104985b40211000000224943cd9f000000000000000000

1 output(s) for total of 338.798971511000 dcy

stealth address amount amount idx
00: 2bfe68d551c7574443b3fafcda6e4b5c1af6038b94379edd901253ccbb5639e4 338.798971511000 143118 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": 77893, "vin": [ { "gen": { "height": 77883 } } ], "vout": [ { "amount": 338798971511, "target": { "key": "2bfe68d551c7574443b3fafcda6e4b5c1af6038b94379edd901253ccbb5639e4" } } ], "extra": [ 1, 249, 52, 194, 137, 176, 87, 16, 113, 215, 92, 157, 207, 39, 222, 96, 130, 0, 156, 181, 75, 84, 110, 208, 157, 35, 36, 237, 200, 16, 73, 133, 180, 2, 17, 0, 0, 0, 34, 73, 67, 205, 159, 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