Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c240fa455aa292069ad356ddc02c930bcc05d6b5141c7e9ea87543a798e1ab0

Tx prefix hash: 83c7ff6edf5493f0792345af6a6ee2a61adafe77bdf53e412360044ba239e81c
Tx public key: fe9e01b37ff1f00ed18c1da402c932f48bf1a4a3f6b682b37c4fddf2bd8bad6e
Timestamp: 1707740518 Timestamp [UCT]: 2024-02-12 12:21:58 Age [y:d:h:m:s]: 00:276:13:26:53
Block: 955916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198003 RingCT/type: yes/0
Extra: 01fe9e01b37ff1f00ed18c1da402c932f48bf1a4a3f6b682b37c4fddf2bd8bad6e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 385fd6641451d30b863b559ddb4d38f2658ec4ee671434bec37b420dbf77f458 0.600000000000 1415216 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": 955926, "vin": [ { "gen": { "height": 955916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "385fd6641451d30b863b559ddb4d38f2658ec4ee671434bec37b420dbf77f458" } } ], "extra": [ 1, 254, 158, 1, 179, 127, 241, 240, 14, 209, 140, 29, 164, 2, 201, 50, 244, 139, 241, 164, 163, 246, 182, 130, 179, 124, 79, 221, 242, 189, 139, 173, 110, 2, 17, 0, 0, 0, 3, 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