Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f236b0af0ef3520ff0fbd7937559dfc0fa671d735b6da9a84fd51c5026c9a36

Tx prefix hash: 7fc93ee535380ee4313a4206e7ce31e10c8723a8ae8463667a2a941611afab22
Tx public key: 0a7d266e9e185c61f11784efdfad79028cf5f8d87245b9ce4bc996ea080739c7
Timestamp: 1644430791 Timestamp [UCT]: 2022-02-09 18:19:51 Age [y:d:h:m:s]: 02:349:13:57:08
Block: 435144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769015 RingCT/type: yes/0
Extra: 010a7d266e9e185c61f11784efdfad79028cf5f8d87245b9ce4bc996ea080739c702110000000137cb3088000000000000000000

1 output(s) for total of 22.191547673000 dcy

stealth address amount amount idx
00: 10f4236ae1bfe2d90a11838334b5e5011e8f66f2474916e49aa4931212b9706b 22.191547673000 846243 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": 435154, "vin": [ { "gen": { "height": 435144 } } ], "vout": [ { "amount": 22191547673, "target": { "key": "10f4236ae1bfe2d90a11838334b5e5011e8f66f2474916e49aa4931212b9706b" } } ], "extra": [ 1, 10, 125, 38, 110, 158, 24, 92, 97, 241, 23, 132, 239, 223, 173, 121, 2, 140, 245, 248, 216, 114, 69, 185, 206, 75, 201, 150, 234, 8, 7, 57, 199, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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