Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f6ca1ff0b1b5346c780296489136a9030b4d0a2cd0695abf7aaa4a86340fd35

Tx prefix hash: 13abe124648e55aec1391521203c17d310f2c304e3664b7fb807b0dfa9f0b33f
Tx public key: f992974ed39f8fdac77b553ca9a67650901930553ea4b0c3a3fd74cb7fe1c2b3
Timestamp: 1729211896 Timestamp [UCT]: 2024-10-18 00:38:16 Age [y:d:h:m:s]: 00:158:20:29:06
Block: 1133932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113296 RingCT/type: yes/0
Extra: 01f992974ed39f8fdac77b553ca9a67650901930553ea4b0c3a3fd74cb7fe1c2b30211000000053cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c477f8a5e0fbad5ad1652371be4cff70bedae72de2c5edfdeaa2c94bf2b6bf56 0.600000000000 1617155 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": 1133942, "vin": [ { "gen": { "height": 1133932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c477f8a5e0fbad5ad1652371be4cff70bedae72de2c5edfdeaa2c94bf2b6bf56" } } ], "extra": [ 1, 249, 146, 151, 78, 211, 159, 143, 218, 199, 123, 85, 60, 169, 166, 118, 80, 144, 25, 48, 85, 62, 164, 176, 195, 163, 253, 116, 203, 127, 225, 194, 179, 2, 17, 0, 0, 0, 5, 60, 208, 252, 6, 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