Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3879cefbbb81addb149fa023d3d4f24654f53e071e13a10439dff920f5eb833c

Tx prefix hash: 33cf8b1a2be516d38ef79b9492b89d684aa8d3b11bdd384a6310f731d10487e5
Tx public key: 9ab5e5d9064df9d9993ed6656616f02f52c5e95dda250dae0732f9211cd828f7
Timestamp: 1737286591 Timestamp [UCT]: 2025-01-19 11:36:31 Age [y:d:h:m:s]: 00:263:01:12:32
Block: 1200682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185488 RingCT/type: yes/0
Extra: 019ab5e5d9064df9d9993ed6656616f02f52c5e95dda250dae0732f9211cd828f7021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be5efb162285e9326c1df27c85d8bc1ce2b2c5e474445f3ac5f6122d63afaaec 0.600000000000 1687327 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": 1200692, "vin": [ { "gen": { "height": 1200682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be5efb162285e9326c1df27c85d8bc1ce2b2c5e474445f3ac5f6122d63afaaec" } } ], "extra": [ 1, 154, 181, 229, 217, 6, 77, 249, 217, 153, 62, 214, 101, 102, 22, 240, 47, 82, 197, 233, 93, 218, 37, 13, 174, 7, 50, 249, 33, 28, 216, 40, 247, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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