Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ebee08c496674066fd89df3977aff9dbe234c2c5095199dcb15a6ab6032254e

Tx prefix hash: 1d4d0ead4f498d4d3cfabb049c9432ccb494cea68dce44377eba0853ce3dd58b
Tx public key: 8bee73bb67a54321f20b47d754237fd96df80add3d6c7706ddaa5d97c70ce9be
Timestamp: 1673437984 Timestamp [UCT]: 2023-01-11 11:53:04 Age [y:d:h:m:s]: 02:138:04:40:58
Block: 672394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 620487 RingCT/type: yes/0
Extra: 018bee73bb67a54321f20b47d754237fd96df80add3d6c7706ddaa5d97c70ce9be02110000000252542ceb000000000000000000

1 output(s) for total of 3.631445307000 dcy

stealth address amount amount idx
00: b8fd66caf8f1a6a0282e32cb74cc72f41a6aede63404da3da34509481e410813 3.631445307000 1113933 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": 672404, "vin": [ { "gen": { "height": 672394 } } ], "vout": [ { "amount": 3631445307, "target": { "key": "b8fd66caf8f1a6a0282e32cb74cc72f41a6aede63404da3da34509481e410813" } } ], "extra": [ 1, 139, 238, 115, 187, 103, 165, 67, 33, 242, 11, 71, 215, 84, 35, 127, 217, 109, 248, 10, 221, 61, 108, 119, 6, 221, 170, 93, 151, 199, 12, 233, 190, 2, 17, 0, 0, 0, 2, 82, 84, 44, 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