Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a321ae22671a5e52c6a83e6d817b56e4aca0c2efe7b81a0c79a80a5f97ad16f2

Tx prefix hash: bf1f125da3b444bddf6a115e8d88ff21f3bb5d3688d1dd7a5908786593d0fb74
Tx public key: d71e37b849ce2c4da4de2fcbed0e624ae74dc3cf19d3f05d582735ede598a49d
Timestamp: 1582513326 Timestamp [UCT]: 2020-02-24 03:02:06 Age [y:d:h:m:s]: 05:010:05:47:12
Block: 71287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160558 RingCT/type: yes/0
Extra: 01d71e37b849ce2c4da4de2fcbed0e624ae74dc3cf19d3f05d582735ede598a49d02110000000103d36d11000000000000000000

1 output(s) for total of 356.284868497000 dcy

stealth address amount amount idx
00: 356eaad9ae0cb991dd11ab32de9d84e44d65a3b2a25c417efa124fd35e2193fd 356.284868497000 131699 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": 71297, "vin": [ { "gen": { "height": 71287 } } ], "vout": [ { "amount": 356284868497, "target": { "key": "356eaad9ae0cb991dd11ab32de9d84e44d65a3b2a25c417efa124fd35e2193fd" } } ], "extra": [ 1, 215, 30, 55, 184, 73, 206, 44, 77, 164, 222, 47, 203, 237, 14, 98, 74, 231, 77, 195, 207, 25, 211, 240, 93, 88, 39, 53, 237, 229, 152, 164, 157, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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