Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5e0e3d3fb23f01dfe33d1cf5fd92725e70ef533d039d44526432d5749d1e5e9

Tx prefix hash: 8a4f547dc23cc193f7c04be17a98fb898cc0eb1c4447a1efa81c4eaf37857a57
Tx public key: af7d183f3f87e1709ffbf88ee255233a14b99897940767bfe3d84981a4d93cab
Timestamp: 1671187134 Timestamp [UCT]: 2022-12-16 10:38:54 Age [y:d:h:m:s]: 02:122:21:36:22
Block: 653767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609524 RingCT/type: yes/0
Extra: 01af7d183f3f87e1709ffbf88ee255233a14b99897940767bfe3d84981a4d93cab0211000000037e406890000000000000000000

1 output(s) for total of 4.185993199000 dcy

stealth address amount amount idx
00: b26de6d678d91d5601e9a5fb8dfcba72f3108d2ce77838ac1c6befb49e99e63c 4.185993199000 1094238 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": 653777, "vin": [ { "gen": { "height": 653767 } } ], "vout": [ { "amount": 4185993199, "target": { "key": "b26de6d678d91d5601e9a5fb8dfcba72f3108d2ce77838ac1c6befb49e99e63c" } } ], "extra": [ 1, 175, 125, 24, 63, 63, 135, 225, 112, 159, 251, 248, 142, 226, 85, 35, 58, 20, 185, 152, 151, 148, 7, 103, 191, 227, 216, 73, 129, 164, 217, 60, 171, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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