Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc725b856808e8903ac5e9be4dc5cfa719929cd26dea15c4ab4b5420f15da6d6

Tx prefix hash: 5ea25f8c98ac42b31f34c0e9c2e2cfd1e4b38b079ebd269e5312e49a3c61c9c1
Tx public key: e90a51e69f9aef3f3ae9a635254c366d19b0cebd6ad857ff37e8bfd8ed04582f
Timestamp: 1705677340 Timestamp [UCT]: 2024-01-19 15:15:40 Age [y:d:h:m:s]: 01:088:12:09:20
Block: 938779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324372 RingCT/type: yes/0
Extra: 01e90a51e69f9aef3f3ae9a635254c366d19b0cebd6ad857ff37e8bfd8ed04582f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 252db0d422141e65f3f1e9557accee0aff4fe8e9132398b9e6b24572a865ebaf 0.600000000000 1396857 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": 938789, "vin": [ { "gen": { "height": 938779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "252db0d422141e65f3f1e9557accee0aff4fe8e9132398b9e6b24572a865ebaf" } } ], "extra": [ 1, 233, 10, 81, 230, 159, 154, 239, 63, 58, 233, 166, 53, 37, 76, 54, 109, 25, 176, 206, 189, 106, 216, 87, 255, 55, 232, 191, 216, 237, 4, 88, 47, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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