Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c05e36edd5b8dc3e5766e6bce07a580feb4104630347ed19b813d4fb9e84bed5

Tx prefix hash: fd58f504d139870dbc717d66f100cca860912e951dd760880e7afa1d1bb0f6ce
Tx public key: 7dd7a734d4cf089b02401bf8934d7990bad9a64fc3bf6136e901d7ac3d61f3d0
Timestamp: 1722747167 Timestamp [UCT]: 2024-08-04 04:52:47 Age [y:d:h:m:s]: 00:240:17:00:24
Block: 1080328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171922 RingCT/type: yes/0
Extra: 017dd7a734d4cf089b02401bf8934d7990bad9a64fc3bf6136e901d7ac3d61f3d002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63ffb3e26bdc863a222a6d8f2c5ff4c53495a408a516a61937f0bcaed9e1de6e 0.600000000000 1553635 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": 1080338, "vin": [ { "gen": { "height": 1080328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63ffb3e26bdc863a222a6d8f2c5ff4c53495a408a516a61937f0bcaed9e1de6e" } } ], "extra": [ 1, 125, 215, 167, 52, 212, 207, 8, 155, 2, 64, 27, 248, 147, 77, 121, 144, 186, 217, 166, 79, 195, 191, 97, 54, 233, 1, 215, 172, 61, 97, 243, 208, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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