Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98cef7617350e972436c5cbc7349d2333b1f0b4ee1dbf831d940a604c326275a

Tx prefix hash: 63ad087ba1e6729b027d66e3164883eea4e9ce9b186a224b113bc1a85014ab23
Tx public key: c2901a1b9642070479245c350d77f4a58834ebe506c2f21b699f4b3c3dec83e8
Timestamp: 1745638678 Timestamp [UCT]: 2025-04-26 03:37:58 Age [y:d:h:m:s]: 00:209:14:12:15
Block: 1269591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147513 RingCT/type: yes/0
Extra: 01c2901a1b9642070479245c350d77f4a58834ebe506c2f21b699f4b3c3dec83e802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 435eaf6cba60fba7b698271e97f5ef815209036f07943bbb50f055c3bf2897b2 0.600000000000 1756830 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": 1269601, "vin": [ { "gen": { "height": 1269591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "435eaf6cba60fba7b698271e97f5ef815209036f07943bbb50f055c3bf2897b2" } } ], "extra": [ 1, 194, 144, 26, 27, 150, 66, 7, 4, 121, 36, 92, 53, 13, 119, 244, 165, 136, 52, 235, 229, 6, 194, 242, 27, 105, 159, 75, 60, 61, 236, 131, 232, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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