Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1473ea6fa895be9e9cd970f2db0250f429c5fcb7baa9c1ea4c39aff4967a00b9

Tx prefix hash: f3664477e5a816ba9dd1e1094c65c9c8dce8db8800d89fdf3496481ce880635e
Tx public key: add1aca1b1847218855fe63322b10096c62e1718c0ddc0d8d24fb08acafa5a25
Timestamp: 1661305806 Timestamp [UCT]: 2022-08-24 01:50:06 Age [y:d:h:m:s]: 02:140:02:06:53
Block: 572461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 621592 RingCT/type: yes/0
Extra: 01add1aca1b1847218855fe63322b10096c62e1718c0ddc0d8d24fb08acafa5a2502110000000475e3f0e9000000000000000000

1 output(s) for total of 7.783934387000 dcy

stealth address amount amount idx
00: 1b40f795cc8f84b5b8613cd6fc2ed24288d91f1cbfcd9c2c5a7e644204dae1f9 7.783934387000 1005711 of 0

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": 572471, "vin": [ { "gen": { "height": 572461 } } ], "vout": [ { "amount": 7783934387, "target": { "key": "1b40f795cc8f84b5b8613cd6fc2ed24288d91f1cbfcd9c2c5a7e644204dae1f9" } } ], "extra": [ 1, 173, 209, 172, 161, 177, 132, 114, 24, 133, 95, 230, 51, 34, 177, 0, 150, 198, 46, 23, 24, 192, 221, 192, 216, 210, 79, 176, 138, 202, 250, 90, 37, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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