Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ab98d251499978791ac5604227ee631f3ee6f7cdd3897f5f803db0eca4c23be

Tx prefix hash: 53ac8355e95e23ecad5764bf6df43f59a32714f473a52adc5ed9f5a2afc0641d
Tx public key: a331f506f55265e93b06eaccaece1d370333b3a7069432876e07aa37bcddbe7b
Timestamp: 1730538480 Timestamp [UCT]: 2024-11-02 09:08:00 Age [y:d:h:m:s]: 01:001:19:30:44
Block: 1144834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259719 RingCT/type: yes/0
Extra: 01a331f506f55265e93b06eaccaece1d370333b3a7069432876e07aa37bcddbe7b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42532f6670f5c7650b131e72dcdb1b46a6dfcf81d3aa47c75fababd5f6d6ecab 0.600000000000 1629161 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": 1144844, "vin": [ { "gen": { "height": 1144834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42532f6670f5c7650b131e72dcdb1b46a6dfcf81d3aa47c75fababd5f6d6ecab" } } ], "extra": [ 1, 163, 49, 245, 6, 245, 82, 101, 233, 59, 6, 234, 204, 174, 206, 29, 55, 3, 51, 179, 167, 6, 148, 50, 135, 110, 7, 170, 55, 188, 221, 190, 123, 2, 17, 0, 0, 0, 2, 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