Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9c422d412d6260ba012f10bd8c00dd84e56a89442e507f2bc0c7636758ad991

Tx prefix hash: f0a6a4cd732e6fb3088ce206c280ca2c9f50afd05eea1aa6c27ce0cdb7748062
Tx public key: 51e11132cbe0feeb12e5afe991d789aa1ab7e3efcb76918cc323d09a308b707e
Timestamp: 1718459713 Timestamp [UCT]: 2024-06-15 13:55:13 Age [y:d:h:m:s]: 00:293:01:40:39
Block: 1044796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209425 RingCT/type: yes/0
Extra: 0151e11132cbe0feeb12e5afe991d789aa1ab7e3efcb76918cc323d09a308b707e0211000000018fff7b1c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 175257609ec91b3154641aba8dd830ade9bf24a5164d52db81fba5d5c409746b 0.600000000000 1514201 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": 1044806, "vin": [ { "gen": { "height": 1044796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "175257609ec91b3154641aba8dd830ade9bf24a5164d52db81fba5d5c409746b" } } ], "extra": [ 1, 81, 225, 17, 50, 203, 224, 254, 235, 18, 229, 175, 233, 145, 215, 137, 170, 26, 183, 227, 239, 203, 118, 145, 140, 195, 35, 208, 154, 48, 139, 112, 126, 2, 17, 0, 0, 0, 1, 143, 255, 123, 28, 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