Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7b366cff4218b5b919fd0d343bcc162f6fbb2004023b5151a6816a90786669a

Tx prefix hash: b1587c095ee1ae0c2f88e593a380bfccfff82c92c5ef4a398ab3ea6b04550ce7
Tx public key: 9f19baa49f5e892bf2de5585ec377124b2962b012eef58fb51c46875b5c3b1d0
Timestamp: 1718123285 Timestamp [UCT]: 2024-06-11 16:28:05 Age [y:d:h:m:s]: 00:174:01:29:10
Block: 1042006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124571 RingCT/type: yes/0
Extra: 019f19baa49f5e892bf2de5585ec377124b2962b012eef58fb51c46875b5c3b1d002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db60ea8decc19a7317746e4c0a47484038af96fdb31e696a1a29500cc1ad26bd 0.600000000000 1510817 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": 1042016, "vin": [ { "gen": { "height": 1042006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db60ea8decc19a7317746e4c0a47484038af96fdb31e696a1a29500cc1ad26bd" } } ], "extra": [ 1, 159, 25, 186, 164, 159, 94, 137, 43, 242, 222, 85, 133, 236, 55, 113, 36, 178, 150, 43, 1, 46, 239, 88, 251, 81, 196, 104, 117, 181, 195, 177, 208, 2, 17, 0, 0, 0, 2, 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