Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7e36023bcd032f7106e328e803b288fd75084e7dbc1d4ca5353327c1c196769

Tx prefix hash: 162e6956f0788fca4bc3a4f42b8614c4ccdbffb9a9f16cea32f35fd424016331
Tx public key: ce85da1e3cf0c2c968cea1e8ade48e1dff132e92a5ae1d8342f34991e4ea6917
Timestamp: 1730559063 Timestamp [UCT]: 2024-11-02 14:51:03 Age [y:d:h:m:s]: 00:143:20:40:56
Block: 1145007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102633 RingCT/type: yes/0
Extra: 01ce85da1e3cf0c2c968cea1e8ade48e1dff132e92a5ae1d8342f34991e4ea69170211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9ded0eb4ad4f19151d7beed855775d34348b4fa69acfa79c98f75d4c0cc7741 0.600000000000 1629366 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": 1145017, "vin": [ { "gen": { "height": 1145007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9ded0eb4ad4f19151d7beed855775d34348b4fa69acfa79c98f75d4c0cc7741" } } ], "extra": [ 1, 206, 133, 218, 30, 60, 240, 194, 201, 104, 206, 161, 232, 173, 228, 142, 29, 255, 19, 46, 146, 165, 174, 29, 131, 66, 243, 73, 145, 228, 234, 105, 23, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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