Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d2b0f78d2e6c58afd865e20be4c3717146fdaa9b22acd7c17b6edbfceacb324

Tx prefix hash: 5e3898e8d013f1ab098c4f63c6c0101d82ae7f129ffd6b06eb47d638b1a8304e
Tx public key: 3582e0e14bd21cfd727ea733e917120e78b1bac78976fda6c337f6c2a385ef88
Timestamp: 1722530482 Timestamp [UCT]: 2024-08-01 16:41:22 Age [y:d:h:m:s]: 00:299:01:35:21
Block: 1078535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213678 RingCT/type: yes/0
Extra: 013582e0e14bd21cfd727ea733e917120e78b1bac78976fda6c337f6c2a385ef88021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dab2c32ed560520374dfd15739ee6000ee01d441ebc2db3f0c30dd84fd625bc1 0.600000000000 1551120 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": 1078545, "vin": [ { "gen": { "height": 1078535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dab2c32ed560520374dfd15739ee6000ee01d441ebc2db3f0c30dd84fd625bc1" } } ], "extra": [ 1, 53, 130, 224, 225, 75, 210, 28, 253, 114, 126, 167, 51, 233, 23, 18, 14, 120, 177, 186, 199, 137, 118, 253, 166, 195, 55, 246, 194, 163, 133, 239, 136, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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