Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01d59f3dcd565146fea1eb06bb0a73ab95fabd2c9caefc883314cf86fa361e76

Tx prefix hash: 25bcaa761db39e731a69444baf9feef2f3429559e12540a53ec8ba352309f803
Tx public key: 5c90bdf458ca6a52797b355350b2f97a6497ba6bad1b0c1efbbc54e78c41156b
Timestamp: 1706640151 Timestamp [UCT]: 2024-01-30 18:42:31 Age [y:d:h:m:s]: 01:342:04:27:22
Block: 946771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503440 RingCT/type: yes/0
Extra: 015c90bdf458ca6a52797b355350b2f97a6497ba6bad1b0c1efbbc54e78c41156b02110000000281d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 801bce2fb0f5f28a22227a2a7c7c9c6ee9e77dc3491dc717921874f31b882add 0.600000000000 1405111 of 15

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": 946781, "vin": [ { "gen": { "height": 946771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "801bce2fb0f5f28a22227a2a7c7c9c6ee9e77dc3491dc717921874f31b882add" } } ], "extra": [ 1, 92, 144, 189, 244, 88, 202, 106, 82, 121, 123, 53, 83, 80, 178, 249, 122, 100, 151, 186, 107, 173, 27, 12, 30, 251, 188, 84, 231, 140, 65, 21, 107, 2, 17, 0, 0, 0, 2, 129, 215, 29, 85, 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