Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c95fcb9e75b211b5f1d74de8812da493c9a880c9fd25e242e8ce5bc9b7dc55

Tx prefix hash: 78c6272f4b1e44c34bbb117fe3f7f4540a624e8754cb2f72cb1ae975005ebfdf
Tx public key: b7652c3ed4e52c5e5780c746d3f2f94aa9165fbf4647cdffcd2e5fb14d975b23
Timestamp: 1721148577 Timestamp [UCT]: 2024-07-16 16:49:37 Age [y:d:h:m:s]: 00:258:21:22:33
Block: 1067098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184925 RingCT/type: yes/0
Extra: 01b7652c3ed4e52c5e5780c746d3f2f94aa9165fbf4647cdffcd2e5fb14d975b2302110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cf5e48301c6b87591e45665744407e651e4cad3e735281d626d682ec60d3184 0.600000000000 1537817 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": 1067108, "vin": [ { "gen": { "height": 1067098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cf5e48301c6b87591e45665744407e651e4cad3e735281d626d682ec60d3184" } } ], "extra": [ 1, 183, 101, 44, 62, 212, 229, 44, 94, 87, 128, 199, 70, 211, 242, 249, 74, 169, 22, 95, 191, 70, 71, 205, 255, 205, 46, 95, 177, 77, 151, 91, 35, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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