Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee3d09f88c5ff2f7cf0ae654114d963ca41480904c9392d2fed0c1dc15ef1e2c

Tx prefix hash: ddf9b3f3083414952e7aeccc3be21a6c4e464f8fbfa0610b1bb76ac5a0f180b7
Tx public key: 8c768d6c7bc00655ed7bdc1b715bcf59b2e1ceb9e81b9698cdb9bd7bff79d9c4
Timestamp: 1615520174 Timestamp [UCT]: 2021-03-12 03:36:14 Age [y:d:h:m:s]: 03:290:05:48:38
Block: 216654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 966844 RingCT/type: yes/0
Extra: 018c768d6c7bc00655ed7bdc1b715bcf59b2e1ceb9e81b9698cdb9bd7bff79d9c402110000010e8c6289e4000000000000000000

1 output(s) for total of 117.530602869000 dcy

stealth address amount amount idx
00: 6a411dbcef99964db6e837ff808a2a2302c85421910d9a376b56280988f1caeb 117.530602869000 444026 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": 216664, "vin": [ { "gen": { "height": 216654 } } ], "vout": [ { "amount": 117530602869, "target": { "key": "6a411dbcef99964db6e837ff808a2a2302c85421910d9a376b56280988f1caeb" } } ], "extra": [ 1, 140, 118, 141, 108, 123, 192, 6, 85, 237, 123, 220, 27, 113, 91, 207, 89, 178, 225, 206, 185, 232, 27, 150, 152, 205, 185, 189, 123, 255, 121, 217, 196, 2, 17, 0, 0, 1, 14, 140, 98, 137, 228, 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