Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b676d961d22df2c1e859b81a57de3fe6f38f07d387afb56431bbc2f198cd1c40

Tx prefix hash: 12dfb7aae5666b189612688f45f818bfb4ab0beb52e7bc7dcfca9fb5f21c2aec
Tx public key: 3489ba3d710e1836fde1f5da1d9c4ea0e21297ec8ff9fbc3d3beb1e9872e7bd0
Timestamp: 1703798104 Timestamp [UCT]: 2023-12-28 21:15:04 Age [y:d:h:m:s]: 01:063:22:20:00
Block: 923233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306777 RingCT/type: yes/0
Extra: 013489ba3d710e1836fde1f5da1d9c4ea0e21297ec8ff9fbc3d3beb1e9872e7bd00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1ce6ac74fbaca08c9683f45824667d0c2f830e5c6e40ce4816b64814042eb4f 0.600000000000 1380961 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": 923243, "vin": [ { "gen": { "height": 923233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1ce6ac74fbaca08c9683f45824667d0c2f830e5c6e40ce4816b64814042eb4f" } } ], "extra": [ 1, 52, 137, 186, 61, 113, 14, 24, 54, 253, 225, 245, 218, 29, 156, 78, 160, 226, 18, 151, 236, 143, 249, 251, 195, 211, 190, 177, 233, 135, 46, 123, 208, 2, 17, 0, 0, 0, 2, 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