Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d147ef3f96ca537c4491b3ffc35b99b438794b36c2d5b262d573e773dc1cdb3

Tx prefix hash: fb88f3eefc4b95bd2972d90b134b4b69c13397a2395194a1d6f1038da66c0f6a
Tx public key: 608573dffe096496d1731b3fd2fb1766eac0ff078dab85e3773c08281aaac0bd
Timestamp: 1719761525 Timestamp [UCT]: 2024-06-30 15:32:05 Age [y:d:h:m:s]: 00:282:07:32:55
Block: 1055568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201723 RingCT/type: yes/0
Extra: 01608573dffe096496d1731b3fd2fb1766eac0ff078dab85e3773c08281aaac0bd02110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52b7e387c6a5fb573d21d869cd3d509cb8d54d9bd5bc01cdc21422934dcf9071 0.600000000000 1525973 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": 1055578, "vin": [ { "gen": { "height": 1055568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52b7e387c6a5fb573d21d869cd3d509cb8d54d9bd5bc01cdc21422934dcf9071" } } ], "extra": [ 1, 96, 133, 115, 223, 254, 9, 100, 150, 209, 115, 27, 63, 210, 251, 23, 102, 234, 192, 255, 7, 141, 171, 133, 227, 119, 60, 8, 40, 26, 170, 192, 189, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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