Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f78aff4d716de7415af48b34d96a7a01da0af0049001635f2493383af329ad3

Tx prefix hash: 64fa48ee368f3a304e74c103c2bd2a61ecefb98f6acc269b97e8c69562798905
Tx public key: 502bb0c95bc0a70f510c7fe7da5782ef2978aa1f8b16a6b7175b62ef76da6866
Timestamp: 1713634062 Timestamp [UCT]: 2024-04-20 17:27:42 Age [y:d:h:m:s]: 01:024:02:49:57
Block: 1004773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278203 RingCT/type: yes/0
Extra: 01502bb0c95bc0a70f510c7fe7da5782ef2978aa1f8b16a6b7175b62ef76da68660211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ebdaf4e0aa4563f8d02c67ad8f41c3c94b7be9a7e05d49a474e283fa9194aa6 0.600000000000 1465347 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": 1004783, "vin": [ { "gen": { "height": 1004773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ebdaf4e0aa4563f8d02c67ad8f41c3c94b7be9a7e05d49a474e283fa9194aa6" } } ], "extra": [ 1, 80, 43, 176, 201, 91, 192, 167, 15, 81, 12, 127, 231, 218, 87, 130, 239, 41, 120, 170, 31, 139, 22, 166, 183, 23, 91, 98, 239, 118, 218, 104, 102, 2, 17, 0, 0, 0, 9, 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