Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59539807c74bca744042eaff4de0a0b716ee55310a7975cf1b2b620c9987480d

Tx prefix hash: 6c8230e2f5154ea7ec56bb245123a83f3e7add28dc1496c77aa71912e3afeb81
Tx public key: 0173b0d323fc6cc8981c5cc70aefddea5009346fb413c3713c2735e256315235
Timestamp: 1718960799 Timestamp [UCT]: 2024-06-21 09:06:39 Age [y:d:h:m:s]: 00:276:02:58:40
Block: 1048924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197318 RingCT/type: yes/0
Extra: 010173b0d323fc6cc8981c5cc70aefddea5009346fb413c3713c2735e25631523502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d42a28875f0c3fafeb741e71ef18e5ff4780b5e5dccc2c6a2b325f71972d0a1 0.600000000000 1519015 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": 1048934, "vin": [ { "gen": { "height": 1048924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d42a28875f0c3fafeb741e71ef18e5ff4780b5e5dccc2c6a2b325f71972d0a1" } } ], "extra": [ 1, 1, 115, 176, 211, 35, 252, 108, 200, 152, 28, 92, 199, 10, 239, 221, 234, 80, 9, 52, 111, 180, 19, 195, 113, 60, 39, 53, 226, 86, 49, 82, 53, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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