Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 739af509f88285525563fee56f66c456e15e25de2aa474a3c2091c2045333c11

Tx prefix hash: 96fccdf28c4b65e4186c19de61462fbb95d3825bab9f4563e6fdd1468f3a7061
Tx public key: 1ef0d2d507213e1bfd3223f72002f9a8781ae09ade64285a52f32ae5b2894307
Timestamp: 1708225062 Timestamp [UCT]: 2024-02-18 02:57:42 Age [y:d:h:m:s]: 01:045:22:26:01
Block: 959927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293865 RingCT/type: yes/0
Extra: 011ef0d2d507213e1bfd3223f72002f9a8781ae09ade64285a52f32ae5b28943070211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f749049461f817a2b42e150d03b4f8e7a2e4d19aec3fb35ecf61320c6b6223a8 0.600000000000 1419486 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": 959937, "vin": [ { "gen": { "height": 959927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f749049461f817a2b42e150d03b4f8e7a2e4d19aec3fb35ecf61320c6b6223a8" } } ], "extra": [ 1, 30, 240, 210, 213, 7, 33, 62, 27, 253, 50, 35, 247, 32, 2, 249, 168, 120, 26, 224, 154, 222, 100, 40, 90, 82, 243, 42, 229, 178, 137, 67, 7, 2, 17, 0, 0, 0, 2, 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