Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ce25cd83d249aedac7cefc78019c2b011d282c54432064f729cc88f72ebf99a

Tx prefix hash: c1065e6b0e38d108cd1f53e4ba0814315af9318379a76e0d0297294159e04fb0
Tx public key: 854df89dcc744b941dcb8a0e9ab419b31c2894f5e43746eab2ad93c8f9f149e6
Timestamp: 1733729692 Timestamp [UCT]: 2024-12-09 07:34:52 Age [y:d:h:m:s]: 00:191:06:45:21
Block: 1171286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136411 RingCT/type: yes/0
Extra: 01854df89dcc744b941dcb8a0e9ab419b31c2894f5e43746eab2ad93c8f9f149e6021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 015089beec59640fd6787a466c8635695dffade3be09fcea278d6c3d0cb58fe8 0.600000000000 1657025 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": 1171296, "vin": [ { "gen": { "height": 1171286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "015089beec59640fd6787a466c8635695dffade3be09fcea278d6c3d0cb58fe8" } } ], "extra": [ 1, 133, 77, 248, 157, 204, 116, 75, 148, 29, 203, 138, 14, 154, 180, 25, 179, 28, 40, 148, 245, 228, 55, 70, 234, 178, 173, 147, 200, 249, 241, 73, 230, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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