Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77abbfe3da3f1673b1f266590a834790888dd872022349d97ed8f5686ec72beb

Tx prefix hash: 76e913b8853eb4a688dd1ab44e218ee37c5caa20b9645656dfb0422ddf6b742c
Tx public key: d0f2460b4df1d8d00b3da0f2dc84e5d86990833895c4e8d51df02ba537ee3e4a
Timestamp: 1735916437 Timestamp [UCT]: 2025-01-03 15:00:37 Age [y:d:h:m:s]: 00:303:20:42:26
Block: 1189387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214650 RingCT/type: yes/0
Extra: 01d0f2460b4df1d8d00b3da0f2dc84e5d86990833895c4e8d51df02ba537ee3e4a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2a03bba8dcdc1bc9a507ed805c7fd6ab0daebd57ced97034c81b8d3172c26fc 0.600000000000 1675896 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": 1189397, "vin": [ { "gen": { "height": 1189387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2a03bba8dcdc1bc9a507ed805c7fd6ab0daebd57ced97034c81b8d3172c26fc" } } ], "extra": [ 1, 208, 242, 70, 11, 77, 241, 216, 208, 11, 61, 160, 242, 220, 132, 229, 216, 105, 144, 131, 56, 149, 196, 232, 213, 29, 240, 43, 165, 55, 238, 62, 74, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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