Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53ccc35a506731eda2b87acfddeea53b2aae252fecb13731ef62ad95b98f4a4

Tx prefix hash: 41bfe33d02033ad89dd7509721c5a89af71acc976f882b4c2dd6b49e462c974c
Tx public key: a9b0f1d537b4723165289dd879fb1fca4b52a5f5397b39ab98c6338a0eaf7731
Timestamp: 1710391787 Timestamp [UCT]: 2024-03-14 04:49:47 Age [y:d:h:m:s]: 00:319:14:46:42
Block: 977920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228516 RingCT/type: yes/0
Extra: 01a9b0f1d537b4723165289dd879fb1fca4b52a5f5397b39ab98c6338a0eaf773102110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96b9610dfd32b8f2da885c99dd557a2a82becdf4d2e4c23da19c741372230210 0.600000000000 1437929 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": 977930, "vin": [ { "gen": { "height": 977920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96b9610dfd32b8f2da885c99dd557a2a82becdf4d2e4c23da19c741372230210" } } ], "extra": [ 1, 169, 176, 241, 213, 55, 180, 114, 49, 101, 40, 157, 216, 121, 251, 31, 202, 75, 82, 165, 245, 57, 123, 57, 171, 152, 198, 51, 138, 14, 175, 119, 49, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 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