Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10f6156e4c9a264bc855c5c7d5e9ec5f863e28933b8f4bbe9b05f27b46f045c8

Tx prefix hash: fe0598fe830fe8a88d7b13b738d14db9b524e66f7c7e280a3582e54e43119e71
Tx public key: 75b917f42f08d8128a1a10421ac65e812ea5e9c96e2d9ddcacdb6e04317a551b
Timestamp: 1738039797 Timestamp [UCT]: 2025-01-28 04:49:57 Age [y:d:h:m:s]: 00:145:22:48:03
Block: 1206705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104171 RingCT/type: yes/0
Extra: 0175b917f42f08d8128a1a10421ac65e812ea5e9c96e2d9ddcacdb6e04317a551b02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd37bb6a26c5feb8c45851938f2505f40c6e5f0c40d29232dc149fc2c0e9af3c 0.600000000000 1693418 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": 1206715, "vin": [ { "gen": { "height": 1206705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd37bb6a26c5feb8c45851938f2505f40c6e5f0c40d29232dc149fc2c0e9af3c" } } ], "extra": [ 1, 117, 185, 23, 244, 47, 8, 216, 18, 138, 26, 16, 66, 26, 198, 94, 129, 46, 165, 233, 201, 110, 45, 157, 220, 172, 219, 110, 4, 49, 122, 85, 27, 2, 17, 0, 0, 0, 10, 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