Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f502b20266329030902294885e63189c6f9003ccc53b358ad3075157c65cdff9

Tx prefix hash: 6a8ea02fe8c11b3c2b1f6e49dbe8fd060465165c7f682b8c2a6663d57bb8f97d
Tx public key: 0b7f3b770122fdf2c23c20190ce0859c5b7a29958b5735a05c008537667538dc
Timestamp: 1717367006 Timestamp [UCT]: 2024-06-02 22:23:26 Age [y:d:h:m:s]: 01:005:15:40:44
Block: 1035737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264942 RingCT/type: yes/0
Extra: 010b7f3b770122fdf2c23c20190ce0859c5b7a29958b5735a05c008537667538dc0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baa629a67e1ac11dbd289b9e6bd52464ae5c4b6e2806b7317a8e9fce6647fde4 0.600000000000 1504260 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": 1035747, "vin": [ { "gen": { "height": 1035737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baa629a67e1ac11dbd289b9e6bd52464ae5c4b6e2806b7317a8e9fce6647fde4" } } ], "extra": [ 1, 11, 127, 59, 119, 1, 34, 253, 242, 194, 60, 32, 25, 12, 224, 133, 156, 91, 122, 41, 149, 139, 87, 53, 160, 92, 0, 133, 55, 102, 117, 56, 220, 2, 17, 0, 0, 0, 6, 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