Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee9af1724c7f60bab37a9dc911671fa2822cc95d069bb7fc748a034b03228ed

Tx prefix hash: 69583fee9a7562f0198f0f59c12070a8d7963970d33c46d613ad77e5eb3a7451
Tx public key: 52602c08afb589d09f6be35aefa59b83cad9b73c2d17e5182055f32ccc53e74a
Timestamp: 1737009594 Timestamp [UCT]: 2025-01-16 06:39:54 Age [y:d:h:m:s]: 00:308:01:21:35
Block: 1198418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217690 RingCT/type: yes/0
Extra: 0152602c08afb589d09f6be35aefa59b83cad9b73c2d17e5182055f32ccc53e74a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cae8a1ca388fb9e8f1e83e914855a0e6b28fe8f5309efb788e6beb67697e14ed 0.600000000000 1685043 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": 1198428, "vin": [ { "gen": { "height": 1198418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cae8a1ca388fb9e8f1e83e914855a0e6b28fe8f5309efb788e6beb67697e14ed" } } ], "extra": [ 1, 82, 96, 44, 8, 175, 181, 137, 208, 159, 107, 227, 90, 239, 165, 155, 131, 202, 217, 183, 60, 45, 23, 229, 24, 32, 85, 243, 44, 204, 83, 231, 74, 2, 17, 0, 0, 0, 1, 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