Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76ae45dc5ad627fb43cf618a3f3c4c17178187cff64134c64aa3f6a9d6ea71e0

Tx prefix hash: cc3ad9ca9d5821f3383a80f357f5c9ed27ad26a60ac38f174d72297a41e40575
Tx public key: 65ea34af151e10163d63e49f9c33d3d2257692aa69ce2854367ace99b45393ca
Timestamp: 1723409565 Timestamp [UCT]: 2024-08-11 20:52:45 Age [y:d:h:m:s]: 00:307:21:23:34
Block: 1085820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219880 RingCT/type: yes/0
Extra: 0165ea34af151e10163d63e49f9c33d3d2257692aa69ce2854367ace99b45393ca021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40c5e07c7b3895a8a3fea8e3d1eb48efb1227a528b8be2f63b68e6b4dadfb288 0.600000000000 1560409 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": 1085830, "vin": [ { "gen": { "height": 1085820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40c5e07c7b3895a8a3fea8e3d1eb48efb1227a528b8be2f63b68e6b4dadfb288" } } ], "extra": [ 1, 101, 234, 52, 175, 21, 30, 16, 22, 61, 99, 228, 159, 156, 51, 211, 210, 37, 118, 146, 170, 105, 206, 40, 84, 54, 122, 206, 153, 180, 83, 147, 202, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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