Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ed8abe993129ab496c624a8dc937d399cc952c91a4992695ca49acce1501087

Tx prefix hash: c526d2b6c8d636f1b7cc271984b8d3a57c7207a9a7b7ac258b26f3fee7bb471e
Tx public key: 8e56bd88a7612f8ba267acbf14458b311f92da03c7875a5619c31493b58dccf8
Timestamp: 1737074960 Timestamp [UCT]: 2025-01-17 00:49:20 Age [y:d:h:m:s]: 00:152:23:59:29
Block: 1198964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109044 RingCT/type: yes/0
Extra: 018e56bd88a7612f8ba267acbf14458b311f92da03c7875a5619c31493b58dccf80211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88121e53d0a95f35e6713a115c5d7cb4bee37810f7a2f084d2c39d877aa683e3 0.600000000000 1685591 of 15

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": 1198974, "vin": [ { "gen": { "height": 1198964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88121e53d0a95f35e6713a115c5d7cb4bee37810f7a2f084d2c39d877aa683e3" } } ], "extra": [ 1, 142, 86, 189, 136, 167, 97, 47, 139, 162, 103, 172, 191, 20, 69, 139, 49, 31, 146, 218, 3, 199, 135, 90, 86, 25, 195, 20, 147, 181, 141, 204, 248, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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