Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b78ec5da502f7adf958d3d53d5b42e02194a6a7491d4cde5224470841f8e16

Tx prefix hash: f0777b8fd889d17afe4292f71d36963f4d9538466a669ae531d7aa14c8301b60
Tx public key: 5583e4da78adfab5cb2ffa147c37c35588e0ad2064a6693fb1aa69294f18d5e4
Timestamp: 1698652660 Timestamp [UCT]: 2023-10-30 07:57:40 Age [y:d:h:m:s]: 01:171:14:16:45
Block: 880795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383645 RingCT/type: yes/0
Extra: 015583e4da78adfab5cb2ffa147c37c35588e0ad2064a6693fb1aa69294f18d5e4021100000003faf35c9c000000000000000000

1 output(s) for total of 0.740560495000 dcy

stealth address amount amount idx
00: 58ad418721253a7518795e4fbfe1c6ecf8b41a3c064338b81e2e3e07a4739fc5 0.740560495000 1336363 of 0

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": 880805, "vin": [ { "gen": { "height": 880795 } } ], "vout": [ { "amount": 740560495, "target": { "key": "58ad418721253a7518795e4fbfe1c6ecf8b41a3c064338b81e2e3e07a4739fc5" } } ], "extra": [ 1, 85, 131, 228, 218, 120, 173, 250, 181, 203, 47, 250, 20, 124, 55, 195, 85, 136, 224, 173, 32, 100, 166, 105, 63, 177, 170, 105, 41, 79, 24, 213, 228, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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