Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f600df7f3ac9e5ccaf5963c1cc77c7ee15963107979810db9b4176c0479409a0

Tx prefix hash: 94d04e832b209e4a343a7d4ef4ba62128e7f095ffef993f07e9298e7f0387a9f
Tx public key: 9bf56b48fbf14cdccab8d729bdf634b510ca73fd208be5697b2d57bbe29905db
Timestamp: 1729577917 Timestamp [UCT]: 2024-10-22 06:18:37 Age [y:d:h:m:s]: 00:097:13:25:46
Block: 1136915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69521 RingCT/type: yes/0
Extra: 019bf56b48fbf14cdccab8d729bdf634b510ca73fd208be5697b2d57bbe29905db0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d4ce6beb478b8a1a86ad32678c14a7d4137d1969f32611d833a6b0c2c10ffcf 0.600000000000 1620312 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": 1136925, "vin": [ { "gen": { "height": 1136915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d4ce6beb478b8a1a86ad32678c14a7d4137d1969f32611d833a6b0c2c10ffcf" } } ], "extra": [ 1, 155, 245, 107, 72, 251, 241, 76, 220, 202, 184, 215, 41, 189, 246, 52, 181, 16, 202, 115, 253, 32, 139, 229, 105, 123, 45, 87, 187, 226, 153, 5, 219, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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