Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 794bdfbf0394ca7998fdf841f28acd3a436901c2c21194ff19f64c6bcefd9016

Tx prefix hash: f3a917d1d5ae735c207a1a4e6e726e2111eebd1be6de1a7652394108dd527b4d
Tx public key: 858f6a92de830d408975d220fe40879e977d119525a7b0897c0da3224f2fa7bc
Timestamp: 1696401760 Timestamp [UCT]: 2023-10-04 06:42:40 Age [y:d:h:m:s]: 01:149:03:21:17
Block: 862113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367607 RingCT/type: yes/0
Extra: 01858f6a92de830d408975d220fe40879e977d119525a7b0897c0da3224f2fa7bc021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.854007707000 dcy

stealth address amount amount idx
00: ab619ece4674a92fec0f50f73f76797b4a75069baad11b1e04fade81af07a7b5 0.854007707000 1316499 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": 862123, "vin": [ { "gen": { "height": 862113 } } ], "vout": [ { "amount": 854007707, "target": { "key": "ab619ece4674a92fec0f50f73f76797b4a75069baad11b1e04fade81af07a7b5" } } ], "extra": [ 1, 133, 143, 106, 146, 222, 131, 13, 64, 137, 117, 210, 32, 254, 64, 135, 158, 151, 125, 17, 149, 37, 167, 176, 137, 124, 13, 163, 34, 79, 47, 167, 188, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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