Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a95e476cb36a36e90c4af90bcea192d38aeecad4f2760628943e75b05b6446a7

Tx prefix hash: e3efe1fc2015236e12cef91489e2165966877162bda9584d525805829aa17a13
Tx public key: e22b13af31436d3a908199c3913fe0c4c4160e32f2ae26443b1e6337d969b21e
Timestamp: 1582444812 Timestamp [UCT]: 2020-02-23 08:00:12 Age [y:d:h:m:s]: 04:322:23:27:15
Block: 70871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123287 RingCT/type: yes/0
Extra: 01e22b13af31436d3a908199c3913fe0c4c4160e32f2ae26443b1e6337d969b21e02110000000256c366d3000000000000000000

1 output(s) for total of 357.423636122000 dcy

stealth address amount amount idx
00: 295ec7287fe2f4ac7af21da8c44c6de5a48873bf8e2fb034bb40e0e2087c5306 357.423636122000 130913 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": 70881, "vin": [ { "gen": { "height": 70871 } } ], "vout": [ { "amount": 357423636122, "target": { "key": "295ec7287fe2f4ac7af21da8c44c6de5a48873bf8e2fb034bb40e0e2087c5306" } } ], "extra": [ 1, 226, 43, 19, 175, 49, 67, 109, 58, 144, 129, 153, 195, 145, 63, 224, 196, 196, 22, 14, 50, 242, 174, 38, 68, 59, 30, 99, 55, 217, 105, 178, 30, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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