Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd54d03b8f1ec36e21e4d2c7294f41d09c19260b8fcd5711a0fc44d20f594470

Tx prefix hash: f5b95a81a69b65f5f14c80557a7f6a3cf87410292583992f25aef7ab0493d455
Tx public key: e9aea7d76e3af073c59ee057eb2e5114a1f0c0cae270f16bb62a6c06d885f9b9
Timestamp: 1704884091 Timestamp [UCT]: 2024-01-10 10:54:51 Age [y:d:h:m:s]: 01:000:08:11:06
Block: 932229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261553 RingCT/type: yes/0
Extra: 01e9aea7d76e3af073c59ee057eb2e5114a1f0c0cae270f16bb62a6c06d885f9b902110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eac3064286564317a224512647124155bf3f4c5a71665819635d88dc4e5b2c06 0.600000000000 1390157 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": 932239, "vin": [ { "gen": { "height": 932229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eac3064286564317a224512647124155bf3f4c5a71665819635d88dc4e5b2c06" } } ], "extra": [ 1, 233, 174, 167, 215, 110, 58, 240, 115, 197, 158, 224, 87, 235, 46, 81, 20, 161, 240, 192, 202, 226, 112, 241, 107, 182, 42, 108, 6, 216, 133, 249, 185, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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