Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ebefa7b3776d0471b820c27fbdcd8371c993cffc07980446e704535f7934acd

Tx prefix hash: f4c7a4d903e6305a0c3954af82e8d377914024f547c7062524e0a1b4195caa35
Tx public key: 8becc99122243a780e96e3774016b9f8f45526091a90cc88838b4e829a7a5d18
Timestamp: 1740800390 Timestamp [UCT]: 2025-03-01 03:39:50 Age [y:d:h:m:s]: 00:335:22:29:07
Block: 1229526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237776 RingCT/type: yes/0
Extra: 018becc99122243a780e96e3774016b9f8f45526091a90cc88838b4e829a7a5d18021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91b0a88a284e652271fe3ff6b7a2b30ad9ef021cc2c6f6ef42fe300c199c1d37 0.600000000000 1716413 of 15

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": 1229536, "vin": [ { "gen": { "height": 1229526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91b0a88a284e652271fe3ff6b7a2b30ad9ef021cc2c6f6ef42fe300c199c1d37" } } ], "extra": [ 1, 139, 236, 201, 145, 34, 36, 58, 120, 14, 150, 227, 119, 64, 22, 185, 248, 244, 85, 38, 9, 26, 144, 204, 136, 131, 139, 78, 130, 154, 122, 93, 24, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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