Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bccc78537473428f7c5ac6f3e675ee2bd8453f1ba776764ec37e57c6589973dc

Tx prefix hash: a44de8fa6c2e0cceb92b475e6bc9d10cb54e9396b6dfcc8ecf61864a19a376a3
Tx public key: 965f317b574dc89de76b40c072cb5af80c73e420bdafc4fd8060b293c0abaad0
Timestamp: 1732693421 Timestamp [UCT]: 2024-11-27 07:43:41 Age [y:d:h:m:s]: 00:134:04:52:57
Block: 1162702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95720 RingCT/type: yes/0
Extra: 01965f317b574dc89de76b40c072cb5af80c73e420bdafc4fd8060b293c0abaad00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6087f5b7c7b8d3845a688431e09909a1937402fb6405b4a16400b5182a75394 0.600000000000 1648359 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": 1162712, "vin": [ { "gen": { "height": 1162702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6087f5b7c7b8d3845a688431e09909a1937402fb6405b4a16400b5182a75394" } } ], "extra": [ 1, 150, 95, 49, 123, 87, 77, 200, 157, 231, 107, 64, 192, 114, 203, 90, 248, 12, 115, 228, 32, 189, 175, 196, 253, 128, 96, 178, 147, 192, 171, 170, 208, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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