Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79f1d4bc9ccc2f6ceaf37d12c584ed4091b6bf1a35d4afc867af1d2e9a82ad21

Tx prefix hash: 7aaec2341506919b980f35fdd72aff2716a9372dc2900ea0501330d4d1e45ce2
Tx public key: 5da25f8212bb711d6524584e646d732df1a82fdef8e417d580f72c000bce34bc
Timestamp: 1737507466 Timestamp [UCT]: 2025-01-22 00:57:46 Age [y:d:h:m:s]: 00:146:23:49:12
Block: 1202507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104795 RingCT/type: yes/0
Extra: 015da25f8212bb711d6524584e646d732df1a82fdef8e417d580f72c000bce34bc021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c54fe1bb427e80db8f65103a725a1f057daa5228765e81b918b2a7849fe66b7 0.600000000000 1689172 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": 1202517, "vin": [ { "gen": { "height": 1202507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c54fe1bb427e80db8f65103a725a1f057daa5228765e81b918b2a7849fe66b7" } } ], "extra": [ 1, 93, 162, 95, 130, 18, 187, 113, 29, 101, 36, 88, 78, 100, 109, 115, 45, 241, 168, 47, 222, 248, 228, 23, 213, 128, 247, 44, 0, 11, 206, 52, 188, 2, 17, 0, 0, 0, 3, 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