Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9cc81d6f8effb431ddc8249679a836b9b683f402c4496a693d466a8835c9cf4

Tx prefix hash: ef077ec5e8a8447e80b4b4563018867a1971a52d4efbe88824f2d1017b9ed915
Tx public key: 324094543fcc1aee2f99badc7eb85c7a4f98cb2693602c6e70964e82a29b943c
Timestamp: 1707740568 Timestamp [UCT]: 2024-02-12 12:22:48 Age [y:d:h:m:s]: 00:276:15:21:33
Block: 955917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198060 RingCT/type: yes/0
Extra: 01324094543fcc1aee2f99badc7eb85c7a4f98cb2693602c6e70964e82a29b943c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d64f0e22c7d56cf779f618af69efb275649e2df10c912c8e99902b9d9e79ede9 0.600000000000 1415217 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": 955927, "vin": [ { "gen": { "height": 955917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d64f0e22c7d56cf779f618af69efb275649e2df10c912c8e99902b9d9e79ede9" } } ], "extra": [ 1, 50, 64, 148, 84, 63, 204, 26, 238, 47, 153, 186, 220, 126, 184, 92, 122, 79, 152, 203, 38, 147, 96, 44, 110, 112, 150, 78, 130, 162, 155, 148, 60, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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