Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6cb8bccc99b5d6a2ccb9670281c18a03e32775a6f920e807114a56cee1b52f1

Tx prefix hash: 8f49427740bfeb8259cd8aaa65fd089e9f61586cb280adcc73188f7eedd95fed
Tx public key: 0ca442cbca1a2a8cb60eea1bfcbd8ebfadb2e77b6d324dafbe2200135c789c89
Timestamp: 1689967648 Timestamp [UCT]: 2023-07-21 19:27:28 Age [y:d:h:m:s]: 01:332:07:50:34
Block: 808836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498544 RingCT/type: yes/0
Extra: 010ca442cbca1a2a8cb60eea1bfcbd8ebfadb2e77b6d324dafbe2200135c789c8902110000000b75e3f0e9000000000000000000

1 output(s) for total of 1.282303079000 dcy

stealth address amount amount idx
00: 4300129fc93afb71baddf0f1d7ba3505794295bb78a2078939273ecadc64bfe2 1.282303079000 1260431 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": 808846, "vin": [ { "gen": { "height": 808836 } } ], "vout": [ { "amount": 1282303079, "target": { "key": "4300129fc93afb71baddf0f1d7ba3505794295bb78a2078939273ecadc64bfe2" } } ], "extra": [ 1, 12, 164, 66, 203, 202, 26, 42, 140, 182, 14, 234, 27, 252, 189, 142, 191, 173, 178, 231, 123, 109, 50, 77, 175, 190, 34, 0, 19, 92, 120, 156, 137, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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