Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de22b505aa8204bba9d5c39543b4d0eeaa5248b090383ea7f65d0c9be011413b

Tx prefix hash: 4516f31c0469c3fef7432dd5fffeb63ca0acb6b78f88282b0d3b8d031074da50
Tx public key: 4f47b4301b2d78caf4bf7024e8f4392e910bdc516e12b2ae2d04427408c8d240
Timestamp: 1696590328 Timestamp [UCT]: 2023-10-06 11:05:28 Age [y:d:h:m:s]: 01:145:08:46:53
Block: 863677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364906 RingCT/type: yes/0
Extra: 014f47b4301b2d78caf4bf7024e8f4392e910bdc516e12b2ae2d04427408c8d24002110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.843877886000 dcy

stealth address amount amount idx
00: 080de155580c81a3843d96de3cf448f1447f7d3761a1f5b54663fdf05b2daeb9 0.843877886000 1318151 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": 863687, "vin": [ { "gen": { "height": 863677 } } ], "vout": [ { "amount": 843877886, "target": { "key": "080de155580c81a3843d96de3cf448f1447f7d3761a1f5b54663fdf05b2daeb9" } } ], "extra": [ 1, 79, 71, 180, 48, 27, 45, 120, 202, 244, 191, 112, 36, 232, 244, 57, 46, 145, 11, 220, 81, 110, 18, 178, 174, 45, 4, 66, 116, 8, 200, 210, 64, 2, 17, 0, 0, 0, 11, 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