Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc02b5e5cb6f031f843b03de3506fc91b1f187b37c46c71ce21f0418a8a4ef9f

Tx prefix hash: f2c9fdd8c4ffa77b953cc473c2bd787a9cf98f43c00aa664bd0ff8467a44bf19
Tx public key: a557ea0a9f0a38d580e2f9027a134f040d4f2b984516b847e3b4186c57f22b37
Timestamp: 1734995823 Timestamp [UCT]: 2024-12-23 23:17:03 Age [y:d:h:m:s]: 00:003:16:06:29
Block: 1181775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2601 RingCT/type: yes/0
Extra: 01a557ea0a9f0a38d580e2f9027a134f040d4f2b984516b847e3b4186c57f22b370211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 143ce164b430a7f5cac6015c9d894123f819efc7aa45feff647dbb53305aab93 0.600000000000 1668200 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": 1181785, "vin": [ { "gen": { "height": 1181775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "143ce164b430a7f5cac6015c9d894123f819efc7aa45feff647dbb53305aab93" } } ], "extra": [ 1, 165, 87, 234, 10, 159, 10, 56, 213, 128, 226, 249, 2, 122, 19, 79, 4, 13, 79, 43, 152, 69, 22, 184, 71, 227, 180, 24, 108, 87, 242, 43, 55, 2, 17, 0, 0, 0, 5, 31, 10, 83, 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