Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60ce17609707887776d816807477c0444d5b8e4a65adef7af7c1666257aff0c0

Tx prefix hash: fa6319d94bc9226c9d4bd25e72a0b5c72e9cd707e9a76c7ee29e7e7fc7ec762e
Tx public key: 545f59a28cd3e4ad53c96714f82977c3bce316633bac8813f9df4c75b08fcd55
Timestamp: 1681424836 Timestamp [UCT]: 2023-04-13 22:27:16 Age [y:d:h:m:s]: 02:047:10:10:42
Block: 737990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556089 RingCT/type: yes/0
Extra: 01545f59a28cd3e4ad53c96714f82977c3bce316633bac8813f9df4c75b08fcd550211000000015029cbac000000000000000000

1 output(s) for total of 2.201622524000 dcy

stealth address amount amount idx
00: 0b1f74c0bd1fdae22d7c236463521ccc05e1d8d0e916a1035ff60a055f04f573 2.201622524000 1184621 of 0

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": 738000, "vin": [ { "gen": { "height": 737990 } } ], "vout": [ { "amount": 2201622524, "target": { "key": "0b1f74c0bd1fdae22d7c236463521ccc05e1d8d0e916a1035ff60a055f04f573" } } ], "extra": [ 1, 84, 95, 89, 162, 140, 211, 228, 173, 83, 201, 103, 20, 248, 41, 119, 195, 188, 227, 22, 99, 59, 172, 136, 19, 249, 223, 76, 117, 176, 143, 205, 85, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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