Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68dc525501241d29ff145cf2144db4d9e87059ed4483655a6b4c850a9546febb

Tx prefix hash: 1dc1b4ef732d5516f6e90dfeb39707f9c91fa37f0a360a93f14152cdc08198a1
Tx public key: 351854c7b6bc256cae351bbb20d81a4d430d0f10db05ef9b4434896013b98ac0
Timestamp: 1719531027 Timestamp [UCT]: 2024-06-27 23:30:27 Age [y:d:h:m:s]: 01:136:01:13:23
Block: 1053661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355785 RingCT/type: yes/0
Extra: 01351854c7b6bc256cae351bbb20d81a4d430d0f10db05ef9b4434896013b98ac00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f895eee8728249b6d60f9711b003f3c4c9d5489c60be83d63d4273f1e3eb9a3 0.600000000000 1524008 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": 1053671, "vin": [ { "gen": { "height": 1053661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f895eee8728249b6d60f9711b003f3c4c9d5489c60be83d63d4273f1e3eb9a3" } } ], "extra": [ 1, 53, 24, 84, 199, 182, 188, 37, 108, 174, 53, 27, 187, 32, 216, 26, 77, 67, 13, 15, 16, 219, 5, 239, 155, 68, 52, 137, 96, 19, 185, 138, 192, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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