Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d8a0f62fd375f124348bb6ae15af056bd697fa061b2e3d4204455a619e5ffa1

Tx prefix hash: 0c9591b60c05f8c837ed2d9cc95359410a17e468f8d84a20f48e3703ff5063d3
Tx public key: 0ddb27d96ccf0734bd4ce4d9a6af5bd77e259ea81281fb64a768c08e3652aba8
Timestamp: 1719819563 Timestamp [UCT]: 2024-07-01 07:39:23 Age [y:d:h:m:s]: 00:277:14:05:24
Block: 1056055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198337 RingCT/type: yes/0
Extra: 010ddb27d96ccf0734bd4ce4d9a6af5bd77e259ea81281fb64a768c08e3652aba8021100000003ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcf01f1ca726690eb4c0a327a159b1391f1609b34aa177a62c40b89a20a80af0 0.600000000000 1526466 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": 1056065, "vin": [ { "gen": { "height": 1056055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcf01f1ca726690eb4c0a327a159b1391f1609b34aa177a62c40b89a20a80af0" } } ], "extra": [ 1, 13, 219, 39, 217, 108, 207, 7, 52, 189, 76, 228, 217, 166, 175, 91, 215, 126, 37, 158, 168, 18, 129, 251, 100, 167, 104, 192, 142, 54, 82, 171, 168, 2, 17, 0, 0, 0, 3, 221, 211, 219, 145, 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