Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98d2c38eb1c72389b7af6d56e314b22a59e56b902507507c7306925f319a91c1

Tx prefix hash: dd2efde6a2f35efab959172ee7359d8b5097fff3ec8463e4cc590ce1e5272bc3
Tx public key: 4595c8737ee58db3a007f143c6d3b59eb86a5467b63cb1c4fbd6352e5b199c98
Timestamp: 1671572653 Timestamp [UCT]: 2022-12-20 21:44:13 Age [y:d:h:m:s]: 02:119:03:49:55
Block: 656952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 606855 RingCT/type: yes/0
Extra: 014595c8737ee58db3a007f143c6d3b59eb86a5467b63cb1c4fbd6352e5b199c9802110000000575e3f0e9000000000000000000

1 output(s) for total of 4.085670675000 dcy

stealth address amount amount idx
00: 2d136db09ebad6f16851e79e4dd1ddd30f61af135d95395c8539deddc17520f4 4.085670675000 1097579 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": 656962, "vin": [ { "gen": { "height": 656952 } } ], "vout": [ { "amount": 4085670675, "target": { "key": "2d136db09ebad6f16851e79e4dd1ddd30f61af135d95395c8539deddc17520f4" } } ], "extra": [ 1, 69, 149, 200, 115, 126, 229, 141, 179, 160, 7, 241, 67, 198, 211, 181, 158, 184, 106, 84, 103, 182, 60, 177, 196, 251, 214, 53, 46, 91, 25, 156, 152, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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