Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f0b9ede36ec7103835944f3fb7ca8b688d2f66664ce910cf17fe2457e5db801

Tx prefix hash: 680e99a16f9f74957fc511db484d6cea59aef5840f9053b294992cc0a4053b41
Tx public key: 1932cc6a0a6545345edbdbcec5ae8d6502be51297581d7d10205c7137b7b238f
Timestamp: 1684849300 Timestamp [UCT]: 2023-05-23 13:41:40 Age [y:d:h:m:s]: 02:010:07:49:11
Block: 766392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529493 RingCT/type: yes/0
Extra: 011932cc6a0a6545345edbdbcec5ae8d6502be51297581d7d10205c7137b7b238f02110000000475e3f0e9000000000000000000

1 output(s) for total of 1.772659566000 dcy

stealth address amount amount idx
00: a2a03fa22a55a014e3098da1dc3cc3e7f8ae8d4385078bee283e3ec513651f39 1.772659566000 1215427 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": 766402, "vin": [ { "gen": { "height": 766392 } } ], "vout": [ { "amount": 1772659566, "target": { "key": "a2a03fa22a55a014e3098da1dc3cc3e7f8ae8d4385078bee283e3ec513651f39" } } ], "extra": [ 1, 25, 50, 204, 106, 10, 101, 69, 52, 94, 219, 219, 206, 197, 174, 141, 101, 2, 190, 81, 41, 117, 129, 215, 209, 2, 5, 199, 19, 123, 123, 35, 143, 2, 17, 0, 0, 0, 4, 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