Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67a372a92c0da14a8c25750ac7d8df6d896b6f020bc72bb86503aaae3d375929

Tx prefix hash: 13e32d3695f44141c33873d819e7224b5b32ad90a44d41e0071adba2e248a8d0
Tx public key: c3e3b9f473caf76532c556dc211a1186904cdaa3995510d0f6956d869e3c8b18
Timestamp: 1712596150 Timestamp [UCT]: 2024-04-08 17:09:10 Age [y:d:h:m:s]: 00:354:13:54:02
Block: 996142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253526 RingCT/type: yes/0
Extra: 01c3e3b9f473caf76532c556dc211a1186904cdaa3995510d0f6956d869e3c8b1802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 198c980099bd38bcb454ba357a51d4e928eb1f2c05ba68c8cfac011e349a4e9f 0.600000000000 1456558 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": 996152, "vin": [ { "gen": { "height": 996142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "198c980099bd38bcb454ba357a51d4e928eb1f2c05ba68c8cfac011e349a4e9f" } } ], "extra": [ 1, 195, 227, 185, 244, 115, 202, 247, 101, 50, 197, 86, 220, 33, 26, 17, 134, 144, 76, 218, 163, 153, 85, 16, 208, 246, 149, 109, 134, 158, 60, 139, 24, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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