Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59336ce56887a8da38d96047bdd478e8e227c4671fcf9404cbbfbc97fa3df6a6

Tx prefix hash: 0ac86f7f18c3b5e2d20010949a8ce5e5f2f8c8016ff00389d5777eac77668b7d
Tx public key: 88cd5c5ad30af6df4dcd3daa5f26b0794eeba848fb4e00367ee856157bc53cdb
Timestamp: 1707647655 Timestamp [UCT]: 2024-02-11 10:34:15 Age [y:d:h:m:s]: 01:035:23:31:19
Block: 955141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286767 RingCT/type: yes/0
Extra: 0188cd5c5ad30af6df4dcd3daa5f26b0794eeba848fb4e00367ee856157bc53cdb02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eec76a1f5e9fde92b1f00e66eb9b5243ab9b883bffd2579769a87baee4bfe683 0.600000000000 1414427 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": 955151, "vin": [ { "gen": { "height": 955141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eec76a1f5e9fde92b1f00e66eb9b5243ab9b883bffd2579769a87baee4bfe683" } } ], "extra": [ 1, 136, 205, 92, 90, 211, 10, 246, 223, 77, 205, 61, 170, 95, 38, 176, 121, 78, 235, 168, 72, 251, 78, 0, 54, 126, 232, 86, 21, 123, 197, 60, 219, 2, 17, 0, 0, 0, 5, 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