Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f95b6df9bdeac04bbffc1b9b3538d7f5e4b861ea69256daa4726452a34e0c1

Tx prefix hash: 4e0688ad73128268145eead7dd1d427a054a72f56e3b3b4e372f6294749480f5
Tx public key: d6aae3a33461b3f519eafc751f1d71ae6431fb73d5f8824f04d4844451073de1
Timestamp: 1702928409 Timestamp [UCT]: 2023-12-18 19:40:09 Age [y:d:h:m:s]: 01:147:10:19:19
Block: 916023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366528 RingCT/type: yes/0
Extra: 01d6aae3a33461b3f519eafc751f1d71ae6431fb73d5f8824f04d4844451073de102110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a56490f6a7bf5118c7fcdfd4511f814495d044c2c46613a5f550609be6d3e59 0.600000000000 1373473 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": 916033, "vin": [ { "gen": { "height": 916023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a56490f6a7bf5118c7fcdfd4511f814495d044c2c46613a5f550609be6d3e59" } } ], "extra": [ 1, 214, 170, 227, 163, 52, 97, 179, 245, 25, 234, 252, 117, 31, 29, 113, 174, 100, 49, 251, 115, 213, 248, 130, 79, 4, 212, 132, 68, 81, 7, 61, 225, 2, 17, 0, 0, 0, 5, 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