Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2425a78f4246c029bc66b59dbf836641adb924aed1a63f6150b889f42494c503

Tx prefix hash: 0dc2427e6a428b46c830c3ccf9f8c2d0c603090a366d1e7f28e47dc36838798f
Tx public key: 047411a92316d4144ea59ce78c6f6410dbd61df3534f455f2b8123787b1a93e5
Timestamp: 1717456678 Timestamp [UCT]: 2024-06-03 23:17:58 Age [y:d:h:m:s]: 00:303:21:04:29
Block: 1036471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217167 RingCT/type: yes/0
Extra: 01047411a92316d4144ea59ce78c6f6410dbd61df3534f455f2b8123787b1a93e502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c19e045ce7f03659558fb1e7f1740309f55c594f24eaca0835c3184b67aaf130 0.600000000000 1504998 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": 1036481, "vin": [ { "gen": { "height": 1036471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c19e045ce7f03659558fb1e7f1740309f55c594f24eaca0835c3184b67aaf130" } } ], "extra": [ 1, 4, 116, 17, 169, 35, 22, 212, 20, 78, 165, 156, 231, 140, 111, 100, 16, 219, 214, 29, 243, 83, 79, 69, 95, 43, 129, 35, 120, 123, 26, 147, 229, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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