Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d125721a36ee7b29598d5e4770632d023ee89b791b234a6fb633382a488ef64

Tx prefix hash: 71a6357c667b71630cbd3047952d56a496dfe954e21dc51f9c3704ae71abf9d6
Tx public key: 8f839f5c9f57ed9dfb0cd2018f66d5bf571cba297785bd78d1be4b7dbeca7140
Timestamp: 1706756561 Timestamp [UCT]: 2024-02-01 03:02:41 Age [y:d:h:m:s]: 01:282:00:17:46
Block: 947744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460344 RingCT/type: yes/0
Extra: 018f839f5c9f57ed9dfb0cd2018f66d5bf571cba297785bd78d1be4b7dbeca714002110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51ab5176a32bc54f42a19b5a1ee1b19a48baa6e1f0d311247a030c62a5228104 0.600000000000 1406102 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": 947754, "vin": [ { "gen": { "height": 947744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51ab5176a32bc54f42a19b5a1ee1b19a48baa6e1f0d311247a030c62a5228104" } } ], "extra": [ 1, 143, 131, 159, 92, 159, 87, 237, 157, 251, 12, 210, 1, 143, 102, 213, 191, 87, 28, 186, 41, 119, 133, 189, 120, 209, 190, 75, 125, 190, 202, 113, 64, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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