Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24657c7253e221ad805dbbee3aa362554bbd18dc14597b338bba24a26ecb7e27

Tx prefix hash: 848700cc8a4ede8b8d29932140e4ad4ca34f62b68558fab7ef89af26c00d9b43
Tx public key: fdf536aa4f17d175751e52fa589dbc1ab3741e0ad8919b77ed0033e261eb0340
Timestamp: 1656330548 Timestamp [UCT]: 2022-06-27 11:49:08 Age [y:d:h:m:s]: 02:233:00:39:41
Block: 531450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687637 RingCT/type: yes/0
Extra: 01fdf536aa4f17d175751e52fa589dbc1ab3741e0ad8919b77ed0033e261eb034002110000000a2e6b1fd5000000000000000000

1 output(s) for total of 10.643530134000 dcy

stealth address amount amount idx
00: c817ddb1926e96b13832e315ac5fb16422d45a8b68d8c64e9783d5a7d66220f5 10.643530134000 960597 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": 531460, "vin": [ { "gen": { "height": 531450 } } ], "vout": [ { "amount": 10643530134, "target": { "key": "c817ddb1926e96b13832e315ac5fb16422d45a8b68d8c64e9783d5a7d66220f5" } } ], "extra": [ 1, 253, 245, 54, 170, 79, 23, 209, 117, 117, 30, 82, 250, 88, 157, 188, 26, 179, 116, 30, 10, 216, 145, 155, 119, 237, 0, 51, 226, 97, 235, 3, 64, 2, 17, 0, 0, 0, 10, 46, 107, 31, 213, 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